fix(iptv): reload EPG during manual playlist refresh - #601
Merged
ProdigyV21 merged 1 commit intoAug 24, 2026
Conversation
Make forced Settings refresh reload playlist and EPG data from the network while preserving cache-only behavior for non-forced loads. Add focused policy coverage for both paths.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The refresh action could finish very quickly while leaving the guide empty or stuck on “Guide pending”, because it forced the playlist but explicitly disabled EPG reload/network fetching.
Testing
IptvRefreshPolicyTest./gradlew :app:compileSideloadDebugKotlin./gradlew :app:testSideloadDebugUnitTestgit diff --checkBehavior note
An explicit manual refresh may take longer than before because it now performs the EPG work the UI promises. Normal startup remains cache-first.
Scope
Android Settings IPTV refresh orchestration only. No startup cache policy, backend, player interaction, catalog, or app version changes.