[BUG] Search Sort By has no effect until another discovery filter is selected
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Read app/src/main/kotlin/com/arflix/tv/ui/screens/search/SearchViewModel.kt, focusing on selectSort, hasDiscoverFilters, and applyDiscoverSelection(). Trace how the discovery browse rows get their ordering and how sort changes reach the filtered grid. Done when changing Sort By in an empty-query browse view updates the displayed discovery results without selecting another filter.
Written by the indexing model from the issue text.
Description
Bug description
In Search → Browse, changing Sort By has no visible effect until another discovery filter, such as a genre, is selected.
Steps to reproduce
- Open Search and leave the text query empty so the discovery browse rows are shown.
- Open the discovery filters and change Sort By (for example, to Top Rated).
- Observe that the browse rows do not reload or reorder.
- Select a genre, then change Sort By again. The filtered grid applies the selected sort.
Expected behavior
Changing Sort By should apply the selected order to the discovery results without requiring an unrelated filter to be selected first.
Actual behavior
Source-code inspection shows that selectSort updates sortOption, but triggers a reload only when hasDiscoverFilters is true. The sort option itself is not counted as a discovery filter. The initial browse rows also carry their own fixed ordering, so changing sort alone leaves them unchanged.
Evidence and verification status
- SearchViewModel.kt (v2.3.1) —
selectSortonly callsapplyDiscoverSelection()whenhasDiscoverFiltersis true; sorting is forwarded to the filtered grid.
These findings are supported by source-code inspection, but this issue was not fully reproduced on a Fire Stick during this investigation.
Environment
- ARVIO v2.3.1
- Amazon Fire TV Stick 4K (2nd Generation, Fire OS 8)
- 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#873 ·
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