mirror of
https://github.com/FluxaMedia/fluxa.git
synced 2026-08-05 00:08:56 +00:00
EpisodeSelected called dataSource.selectEpisode(episodeId), which kicks off DetailViewModel.fetchStreamsForSelection, and then also emitted a SelectSources navigation event that FluxaAppHost handles by calling detailStore.loadSources(episodeId) -- which starts the exact same fetch again. fetchStreamsForSelection cancels its previous job on every call, so the second (navigation-triggered) fetch always killed the first one before its addon requests could resolve, and the episode's stream list came back empty even though the addons genuinely had results (confirmed via logcat: StreamDiscovery reports 600 remote streams found, then the very next fetch attempt logs "NO STREAMS found" for the same episode). loadSources already does everything selectEpisode did (marks the episode selected, then fetches), so the direct selectEpisode call is redundant -- drop it and let the single navigation-driven fetch run uncontested. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle.kts | ||