We've received reports that removing the currently playing song from the playlist and reordering the queue breaks it.
Thanks to @qiiwexc for providing a video of the issue!
Thank you for reporting this issue to us.
We just wanted to let you know that the right folks are looking into this.
We're not able to provide an exact timeline for a fix, but we'd recommend always keeping your Spotify app up to date to ensure you're on the latest version.
1. iPhone 12 Pro, pretty sure this also was present on iPhone Xs
2. A Windows laptop
1. iOS 15 Developer Beta 1, but this was also an issue on iOS 14.x
2. Windows 10 64-bit (10.0.19042.1052), Google Chrome 64-bit (91.0.4472.101)
My Question or Issue
Steps to reproduce:
1. Start playback of any song in any playlist
2. Remove this currently playing song from that playlist
3. Open "Next From" section and reorder songs there
User's order is applied, just like when it is when no songs were removed
The queue gets somewhat randomized each time the order is changed, yet it doesn't look like a shuffle, but rather like it has some logic to it, but it's flawed. I guess the length of some array is not updated after the song is removed?
On the attached video I first show the case then queue reordering works correctly - when just playing a song without removing anything, then I go through the steps described above.
This issue has been there for a really long time, half a year for sure, so it's not a recent regression.
P.S. I have just tested this on web player and it's the same, so I suppose the issue is on the backend.
Thanks for reporting this issue to us.
We’ve passed your info on to the relevant team, who are currently looking into it.
If you’re experiencing this issue, make sure to click +VOTE and Subscribe to the thread to be notified of any developments.
Could you also make sure to provide us with the following info, if you haven’t already:
Thanks! We’ll keep you posted and let you know as soon as we have any updates on this.
Spotify version 188.8.131.528, but the bug was there for many versions already
Late to the party, but also experiencing this issue on 184.108.40.2063.gdac868ed-a desktop client, Windows Pro version 10.0.19042.
How do I post my own thread? There is no direction