[BUG] Xtream VOD sources in Details bypass quality regex filters
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- backend, mobile-dev
Research direction
Start with the Xtream VOD append path in app/src/main/kotlin/com/arflix/tv/ui/screens/details/DetailsViewModel.kt, then compare how StreamRepository.kt applies quality regex filters on other source paths. Check the Details source list with matching CAM and TELESYNC entries after applying the configured filters; done means those entries are excluded consistently. The issue notes that on-device playback handoff still needs verification.
Written by the indexing model from the issue text.
Description
Bug description
Xtream IPTV VOD sources appear in the Details screen without consistently respecting the configured quality regex filters. This can leave poor-quality releases such as CAM and TELESYNC in the source choices even when the user has configured filters to exclude them.
Steps to reproduce
- Add an Xtream playlist that has a movie or episode available in multiple VOD versions, including a title/source marked CAM or TELESYNC.
- Configure the quality regex filters to match and exclude CAM and TELESYNC.
- Open that movie or episode in ARVIO and wait for Xtream VOD sources to load in Details.
- Check whether the matching CAM/TELESYNC Xtream source is still listed.
Expected behavior
Xtream VOD choices should be filtered using the configured built-in and custom quality regex rules before they are shown or offered for playback, consistently with other stream sources.
Actual behavior
Source-code inspection indicates that the asynchronous Xtream VOD append path in DetailsViewModel resolves movie/episode VOD sources and merges them into the Details source list without calling applyQualityRegexFilters. The filtering helper is used on other source paths in StreamRepository. The player has a separate provider lookup, so the exact playback effect still needs runtime confirmation.
Evidence and verification status
- DetailsViewModel.kt (v2.3.1) — Xtream VOD sources are appended to the Details list.
- StreamRepository.kt (v2.3.1) — quality regex filtering is applied on other resolution paths.
These findings are supported by source-code inspection, but this issue was not fully reproduced on a Fire Stick during this investigation. In particular, the on-device source list and final playback handoff were not both verified.
Environment
- ARVIO v2.3.1
- Amazon Fire TV Stick 4K (2nd Generation, Fire OS 8)
- Xtream IPTV VOD playlist
- Dominant language
- Kotlin
- Stars
- 760
- Forks
- 122
- Avg merge
- 16h 47m
- Merged PRs (30d)
- 65
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ProdigyV21/ARVIO
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ProdigyV21/ARVIO#874 ·
Maintainers usually reply within 1 day
-
area: web type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
ProdigyV21/ARVIO#444 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ProdigyV21/ARVIO#367 · 1 comment ·
Maintainers usually reply within 1 day
-
type:bug
Difficulty 3/5 1-2 days Newbie friendliness 25/100
ProdigyV21/ARVIO#857 ·
Maintainers usually reply within 1 day
-
type:feature
Difficulty 3/5 1-2 days Newbie friendliness 58/100
ProdigyV21/ARVIO#851 ·
Maintainers usually reply within 1 day
All issues in ProdigyV21/ARVIO
Similar issues
-
bug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Source: c7 Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Submission] AI通话助手Opensubmit-adaption submit-adaption-pre
Difficulty 1/5 Under an hour Newbie friendliness 88/100
BetterAndroid/android-notification-icon-project#828 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
user-grinch/RivoPhoneApp#358 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day