Capture the smallest repeatable trigger
Try to describe a short sequence that causes the close, such as opening a particular guide or starting one source. Note whether another account or programme behaves differently only if you can test it safely.
Record the device model, system version and app version before changing anything. A photograph of a version screen should exclude account credentials.
Check supported updates and available storage
Use the device and publisher's official update route. Verify that the current app still supports the operating system. Inspect available storage through the device's own tools rather than installing an unknown cleaner.
If an update or storage change helps, repeat the same trigger. Do not claim a fix from an unrelated successful programme.
Preserve data before reinstalling
Learn what the app stores locally and whether favourites or account details can be retained through supported means. Clearing data or uninstalling may erase them.
If the crash remains reproducible, send the trigger and version details to the app publisher or provider's supported app team. A crashing interface is not automatically a broadband or subscription-expiry issue.
Distinguish a crash from a playback pause
A crash usually returns you to a device home screen, closes the program window or causes the application to restart. A loading indicator with the app still responsive is a different symptom. Write down which one happens and whether the device's own menus continue to work.
If the whole television restarts or loses its ordinary interface, include that wider behaviour. An app-specific guide should not disguise a device or power problem as a content-account issue. Preserve any visible message before trying recovery.
Reproduce the smallest meaningful action
Start from the normal app opening and note the shortest sequence that triggers the exit. Examples include selecting the guide, opening one category or beginning one programme. These are possible reporting patterns, not claims about a particular player.
Try one different available item if the app remains usable long enough. If only a named programme triggers the crash, retain that fact. If it closes before you enter an account, say so. A developer investigating first launch needs different information from a provider investigating one source.
Match the crash pattern to useful evidence
Collect the actual result rather than assuming the cause from a familiar symptom.
| Pattern | What to record | Relevant next route |
|---|---|---|
| Closes on opening | Device, system, app version and error | Publisher's supported compatibility and recovery guidance |
| Closes when guide opens | Steps and whether other menus work | Player or supported app team |
| Closes on one programme | Source name, time and another-source result | Provider and player information together |
| Several apps close or device restarts | Wider affected functions and any warning | Device manufacturer's guidance |
| Fault begins after an update | Old and new versions if known, first occurrence | Publisher's current support information |
Use non-destructive platform checks first
Google's TV guidance and Apple's app guidance provide platform-specific restart and update routes. Use the instructions for the device you actually have. A normal app close, a device restart and removal of app data are different actions and should not be treated as synonyms.
Check official app and system updates when appropriate, keep power stable during an update and test the same trigger afterwards. If the app is no longer supported on that operating system, repeated reinstalls will not establish compatibility. Ask the publisher about a supported alternative.
Prepare recovery before clearing data
Identify how the application stores accounts, favourites and any recordings. A supported export may contain credentials, so keep it private. If no safe export exists, preserve the legitimate account-recovery route and note essential favourites without recording the secret in a shared document.
Read the warning on the actual reset or uninstall action. Do not clear data simply because a menu offers it. If a documented support step requires it, understand what will be removed and how the configuration will be restored before accepting.
Make the support report easy to reproduce
Send a short numbered sequence in ordinary language, followed by the observed outcome. Include the exact device and app versions, local time, source when relevant and one comparison. Remove full account URLs from screenshots or logs.
For an Irish household switching among official broadcaster apps and a separate player, name the application explicitly. A problem in one does not establish a general television outage. If the issue stops reproducing, report that limited result and the change made rather than claiming a permanent fix.