Some channel groups are missing: diagnostic checklist for Apple iPad
Some channel groups are missing on Apple iPad: isolate the device, player, network and source with a clear test sequence and support checklist.
What this symptom means on Apple iPad
The library loads, but one expected group or category cannot be found. This runbook applies when you are already using a player or viewing method supported by the actual device. Begin with one reproducible example; the symptom by itself does not prove that a service, application or network is at fault.
Check the Apple iPad environment
Use the installed app’s supported input method and the device’s normal network settings. App availability and features differ between iPhone, iPad and Apple TV.
- Record the OS version and the app version from the device or app information screen.
- For an external display or audio route, compare native playback before testing casting or wireless audio.
- Check the store listing for your exact Apple device and avoid instructions intended for sideloading an Android APK.
Identify the full playback chain before testing: device, operating system, player, login format, local connection and destination display or audio route. For an external box, a television may be only the display. In that case, the app version and network measurements belong to the box.
Run a controlled diagnostic sequence
- Remove a temporary category filter and check hidden groups.
- Compare the same account’s group list on one other supported device.
- Confirm the expected category is included in the current account terms.
- Refresh the source once and note whether the missing group appears.
Carry out the steps in order while keeping other settings unchanged. Write down the initial result and the result after each change. If a test has no measurable benefit, restore its original setting before continuing. This gives support a history it can interpret and avoids ending with several unexplained adjustments.
Possible explanations to compare
- Local filtering or an outdated cached list
- Changes to the source categories
- An account that does not include the requested group
These are hypotheses to test, not a diagnosis. A problem that follows an account across two otherwise working devices points to a different layer than a problem limited to one app. A failure seen only over one local connection needs a network comparison before an account reset.
What to record for support
| Evidence | Record | Keep private |
|---|---|---|
| Device | Apple iPad, exact model and operating system build | Serial numbers and account-linked identifiers |
| Player | Publisher, version and selected login type | Password, full playlist URL or portal token |
| Failure | Some channel groups are missing, exact message and local timestamp | Customer or payment details |
| Comparison | Which single change improved or reproduced the result | Credentials for the comparison account |
A useful report includes what still works. For example, say whether menus respond, another item plays, or a second connection produces the same result. Avoid a screenshot of the full account page when a cropped error message is enough.
Work through the checklist
The checklist on this page is a temporary working aid. Record your final results in your own notes if you need to keep them or send them to support.
When to stop and escalate
A channel name is not proof of availability or regional access. Ask support about the specific group using your account reference privately.
Stop changing settings when you can reproduce the failure and explain the controlled comparison. Send the evidence privately to the relevant app publisher or service operator. If the feature is unsupported on this model, document that finding and use a supported alternative rather than repeating the same reset.
Related Apple iPad reference
Read the Apple iPad device guide for setup context, and use the community discussion area to share a redacted description of your test.