Wrong song plays after searching and selecting a track
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
The payload names no source files, so start by reproducing the bug in a local build: open a playlist, filter it with search, tap a track, and check which track starts. Then find where the playback queue is built from the search results and where the tapped index is passed on. Done means the track tapped in a filtered playlist is the one that plays, and the steps in the issue no longer produce a random song.
Written by the indexing model from the issue text.
Description
Required pre-submission checklist
- I have searched existing issues to ensure this is not a duplicate.
- I tested this bug on the latest available build (preferably Canary).
- This report describes one specific bug, not multiple unrelated problems.
- The issue title names the affected area and the broken behavior clearly.
Release channel
Canary / Actions build
YumaPlayer version & build
Canary.20261101
Affected area
Library / playlists / local media / FLAC
Reproducibility
Every time
Steps to reproduce
- Open yuma player
- Head to library
- Click the playlist section
- Then search inside any playlist
- Then click the song
- Volla! A random song plays
Expected vs actual behavior
Expected: it should have played the song I clicked
Actual behaviour : it starts to play random song
Logs / Crash trace
No response
Screenshots or screen recordings (optional)
https://github.com/user-attachments/assets/c780aeda-1a63-4c49-ae15-33f006455450
Android version
Android 15
Device model
Poco m6 5g (Xiaomi hyper os 2.0.208.0)
Additional context
No response
- Dominant language
- Kotlin
- Stars
- 681
- Forks
- 22
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 20
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 MuwMx/YumaPlayer
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MuwMx/YumaPlayer#163 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
MuwMx/YumaPlayer#98 ·
Maintainers usually reply within 3 days
-
No feed and no queueOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MuwMx/YumaPlayer#167 · 3 comments ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
MuwMx/YumaPlayer#162 · 2 comments ·
Maintainers usually reply within 3 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MuwMx/YumaPlayer#158 ·
Maintainers usually reply within 3 days
All issues in MuwMx/YumaPlayer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
liberation-data/drivine-cypher-spec#67 ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
documentation good first issue help wanted P2 roadmap-v4
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
maziyarpanahi/openmed#5425 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OneBusAway/vehicle-positions#250 ·
Maintainers usually reply within 1 day
-
android cleanup good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 86/100