Device/OS: Windows 10, Desktop app & browser versions
Issue: Double clicking a playlist set to shuffle does not play that playlist shuffled anew. If I am currently playing a track in Playlist 1 and I double click it, Spotify will now start playing from the start of whatever play queue it had previously generated from that playlist. It will not, as it did yesterday and every day before that for the longest while now, generate a new queue and play it. It started happening today.
Spotify desktop verion: 1.2.98.301.gfcaeba72
Observations:
- Double clicking a different playlist from one that is currently queued does generate a new queue of that new playlist as before.
- Double clicking that new playlist again just restarts playing from the start of that new queue.
- I can circumvent the bug or "feature" by playing a different playlist first, then double clicking the desired playlist, because only then will the app generate a new shuffled queue.
- If I skip currently played song of a newly generated queue, double clicking will play the first song of the generated queue, and double clicking again will play the 2nd song of the generated queue, then double clicking again will play the 3rd song, etc, until all skipped songs have been replayed, after which it will go back to the 1st one again.
- If I have a shuffled queue of tracks in order of 2, 4, 1, 3, then skip track 2 before double clicking again, it will first play track 2, then another double click will play track 4, and double clicking again will play track 2. If I skip the entire queue of these track, it will without fail play on double clicks in the order the queue had set the tracks.
Speculation: Something has gone wrong with queue generation rather than the shuffle feature itself.
Cross Device Observation: If I play a new shuffled queue on my phone (android) while the desktop app is on, and then double click same playlist on the desktop app, it replicates the issue in the exact same manner. As there is no way to "shuffle play" from a playlist you're currently already listening from on the mobile app, I cannot comment if this is a device issue or a backend issue. I suspect the latter because the exact same issue happens in the web browser version on desktop, but that may be beacuse it literally just plays the desktop app in browser. (That or the desktop app is actually just a customized browser window)