Describe the import result
Note whether the app rejects the address, stays loading, displays groups without channels or shows channels that will not play. These are different outcomes and help support identify the relevant stage.
Keep the original file or URL privately. Do not paste it into an online validator that may receive account credentials.
Verify the supported source
Check with the provider that the account is active and the supplied method is supported by the player. A downloaded web page saved as a playlist file will not necessarily be valid playlist data.
If the provider issues a replacement address, identify which saved entry is current so old and new playlists are not confused. Avoid deleting the only working configuration before recording the change.
Refresh without losing the household setup
Check the app's refresh instructions and how favourites are stored. Re-importing a large catalogue can create duplicates or orphan favourites if the identifiers changed.
After refresh, test one known available source. If the catalogue appears but only a particular channel fails, move to source-specific troubleshooting rather than repeating the whole import.
Identify the stage at which import stops
Separate an address rejected immediately, a download that never finishes, an import that returns zero entries and a list that appears but will not play. They are different outcomes. Note the app's exact message and whether the same source worked previously.
Do not delete a working account merely because one new import fails. If the player supports multiple sources, label them clearly and keep the known working one unchanged while investigating. If it does not, confirm a supported backup or recovery method before replacing its current configuration.
| Outcome | Focused check | What it does not prove |
|---|---|---|
| Address rejected before loading | Supported field and input syntax | That the provider's entire service is offline |
| Import starts but fails | Account state, authorised endpoint and exact error | That the file must be manually edited |
| Zero entries reported | Expected source type and supplied catalogue | That every channel has stopped broadcasting |
| Entries appear but video fails | Playback entitlement and one known available item | That the playlist parser failed |
| Some groups are missing | Filters, source scope and refresh state | That a reinstall will add them |
| Old favourites fail after refresh | Current entry versus saved shortcut | That the current catalogue is necessarily broken |
Confirm what kind of source was supplied
A local playlist file and a remote playlist address behave differently. A saved file is a snapshot; a remote address may retrieve a current version when the player refreshes. Use the method the provider and app actually support rather than changing the extension or copying contents between formats.
The HLS specification uses playlists to describe a media presentation, including segments or variants. Consequently, an M3U8-looking address is not automatically a multi-channel catalogue. If a supplied item opens one programme rather than a channel list, ask what it is intended to represent before calling the import incomplete.
Check the input carefully and privately
Compare the address with the original private instructions, including its beginning, path and any supplied parameters. Do not remove a token, username or query component because it looks unnecessary. Conversely, do not paste a whole address into separate credential fields unless the app's documented method calls for that.
Avoid public playlist validators and search engines for credential-bearing material. A safe support note can identify the method and redacted source label without publishing access. If the address was exposed, ask the provider about revocation or regeneration; deleting a forum post does not guarantee that nobody copied it.
Use the player's supported import route
VideoLAN documents opening supported network media in VLC, but that does not establish every provider's catalogue or guide workflow. Use the documentation for the exact player and platform. A desktop instruction can differ substantially from a television app's account-entry screen.
Before clearing an app database, find out whether favourites, guide associations and account details are stored there. Prefer a documented source refresh if that is the appropriate action. Keep the old update time and compare a small representative set afterwards instead of assuming a progress spinner proves the correct catalogue arrived.
Validate a small sample after the list appears
Choose a current authorised item from each important group rather than attempting to play every entry. Check that the displayed name corresponds to the video and that the household's required controls work. A successful import count is not a content-rights certificate or proof that every listed stream is available.
If one old favourite fails but the current entry works, rebuild that shortcut through the app's supported controls. If the new entry fails too, preserve the exact name and error for the service. Keep guide problems separate: a channel can play while its schedule data is absent or incorrectly associated.
Send a compact import report
Include the app, version, device, input method and import result. State whether the source was supplied as a file, address or structured account fields, without including the secret values. Add whether any entries appeared and whether a known available item played.
For example: 'Supported URL import completes and shows entries; one current source plays; saved favourites from the old import fail; no app data cleared.' This fictional note points to a narrower next check than playlist broken. Support can then ask for the relevant private details through its appropriate channel if needed.