[BUG] Queue injection ignored when starting playback from a Playlist (Queue State Conflict)

[Francesco-rainone]

Hey @HemantKArya, I've encountered a specific issue regarding the playback logic that affects the core experience on both Android and Windows.

The "Play Next" and "Add to Queue" features seem to stop working depending on how the playback is initialized. Even though the app shows the "Added!" confirmation toast, the actual queue remains unchanged if the session started from a Playlist.

---

The Issue

I've noticed a conflict between the Playlist controller and the Manual Queue:

• The Bug: If I start a song directly from an imported Playlist (Spotify/YT Music), the player seems "locked" to that playlist's sequence. Any attempt to "Play Next" a new track is visually confirmed by the UI but ignored by the audio service. The player just continues with the next song in the original playlist.
• The Workaround: The queue works perfectly if I start a song that isn't part of a playlist, or if I manually add songs to the queue before hitting play.

It seems like starting from a playlist creates a "Read-Only" sequence that doesn't allow external injections.

---

Steps to Reproduce

1. Open any Playlist and tap a song to start playback.
2. Find another track, tap the menu, and select "Play Next" or Add to queue.
3. Observe the "Added!" toast.
4. Check the queue or wait for the song to end: the player skips your queued song and follows the original playlist order.

Visual Evidence

I'm attaching a video showing the "Added!" confirmation and the subsequent queue state, demonstrating that the track added to the queue is not being processed properly.

video showing wrong queue state

20260215-2254-04.7286353.mp4

---

Technical Context & Alignment

• Platform: Confirmed on Android + Windows (Cross-platform logic issue).
• Why it's not a duplicate: I've checked Shuffle Queue not visible and Play next not working. #200, Imported music playlist from Spotify can't be seen anywhere  #187, and Add an option to clear the existing queue (up-next) #307. This isn't a UI bug or an import failure, but a state management conflict in the playback engine.
• Potential Cause: It likely happens because the AudioService stays bound to the Playlist array and doesn't sync with the CustomQueue state when initialized from a playlist view.

---

Note

I'm open to providing logs or further testing if you need more details to isolate this.