[UI Bug] Home navigation button not selected after pressing Back from Mix, Library, or Search
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by tracing Back navigation from Mix, Library, and Search to the Home page, then inspect how the selected navigation item is updated for those destinations. Reproduce on Android 11 using the listed steps and check the navigation UI after returning Home. Done when the Home page is displayed and its navigation button is selected.
Written by the indexing model from the issue text.
Description
Duplicate Check
- I confirm I searched for existing reports and found no duplicates.
Latest Release
- I confirm I am on the latest release and the problem still happens.
Describe the Bug
When navigating to the Mix, Library, or Search page and pressing the device’s Back button, the app returns to the Home page, but the Home navigation button does not appear selected.
Steps to Reproduce
- Navigate to the Mix, Library, or Search page.
- Press the device’s Back button.
- Observe that the app returns to the Home page.
- Check whether the Home navigation button is selected.
Expected Behavior
The selected navigation item should reflect the currently displayed page, so the Home button should be selected automatically when the app returns to Home.
App Version
2.3.0
Android Version
Android 11
Device Model
Samsung Galaxy M30s
Custom ROM
- I am using a custom ROM
Custom ROM Name (if applicable)
No response
Screenshots (optional)
https://github.com/user-attachments/assets/611b6e12-b4a7-4689-9d7b-22043de53868
Log / Error Details
No response
- Dominant language
- Kotlin
- Stars
- 12.4k
- Forks
- 696
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 maxrave-dev/SimpMusic
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
maxrave-dev/SimpMusic#2746 ·
Maintainers usually reply within 3 days
-
bug:unconfirmed
Difficulty 2/5 Under an hour Newbie friendliness 65/100
maxrave-dev/SimpMusic#2684 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
maxrave-dev/SimpMusic#2661 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
maxrave-dev/SimpMusic#2652 ·
Maintainers usually reply within 3 days
-
[UI/UX] Keyboard does not dismiss automatically after selecting a song from searchPossibly taken @SiddartthVS claimed this 32 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maxrave-dev/SimpMusic#2507 ·
Maintainers usually reply within 3 days
All issues in maxrave-dev/SimpMusic
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PixelPlayerHQ/PixelPlayerOSS#193 ·
Maintainers usually reply within 1 day
-
bug web-server
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jooby-project/jooby#4035 ·
Maintainers usually reply within 1 day
-
Android: theme prop is ignored in R8-minified release builds (Theme enum is not Enumerable)Possibly taken @1kuko3 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
keiyoushi/extensions-source#20494 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100