No feed and no queue
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
The report identifies the homepage mixes and playback queue as affected areas but names no files or tests. Start by reproducing on Android 17 with YumaPlayer 1.2.0-RC.1, then trace the homepage content and queue behavior after a track ends. Done means the homepage shows the expected mixes and listening sections, and a queue continues after playback finishes.
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
Stable
YumaPlayer version & build
Stable 1.2.0-RC.1
Affected area
Music player / now playing / miniplayer
Reproducibility
Every time
Steps to reproduce
- Open Yuma
- What should be Mixes and more than quick picks is a mostly empty homepage
- Upon listening to a song and letting it finish, does not make a queue based on that song
Expected vs actual behavior
Expected: Homepage with mixed, keep listening and listen again and for a queue to be made after a song finishes
Actual: empty homepage with only quick picks and only plays one song and no more
Logs / Crash trace
No response
Screenshots or screen recordings (optional)
https://streamable.com/if6gis
Attaching it didn't work :/
Android version
Android 17
Device model
Nothing
Additional context
Happens after a couple days of use, stays like this until cleared storage then usually happens again
- 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
-
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
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
MuwMx/YumaPlayer#136 · 3 comments ·
Maintainers usually reply within 3 days
All issues in MuwMx/YumaPlayer
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
liberation-data/drivine-cypher-spec#67 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
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