When playback changes immediately after an app update, the timing is useful evidence but does not establish the cause by itself. Keep a record of the player version and the exact action that now fails. A focused comparison gives support more to investigate than a general claim that the entire subscription stopped working.
Describe what changed
Record the device model, operating system and new player version. Note whether login, catalogue loading, video, sound or navigation is affected. If you remember the earlier version, include it without guessing. Preserve the account details and any local preferences before considering a reinstall, because reinstalling may remove the evidence or the saved setup.
Repeat a small test
Try a known channel and an on-demand item without changing the network. Check whether the issue occurs everywhere or only in one playback mode. If another supported player is already configured, its result may provide context; do not purchase a new app just to create a comparison. Change only a setting that support or the publisher identifies as relevant.
Use supported recovery options
Check the publisher’s release notes or support channel for the reported behaviour. Avoid downloading an older installer from an unknown site. If a supported rollback or replacement is recommended, confirm how to preserve and restore the configuration first. Send the exact error and the comparison results so the next step is based on the observed failure.
Your checklist
- Record app and device versions.
- Separate login, catalogue and playback failures.
- Use the publisher’s supported recovery guidance.
What to take away
Update timing is a clue, not a complete diagnosis. Keep the setup recoverable and provide a reproducible example before changing credentials or replacing the player.