topic Re: Move up feature in queue creates duplicates in Android

Move up feature in queue creates duplicates

Simply_Samps — Sun, 22 Feb 2026 00:15:15 GMT

Plan

Premium

Country

United Kingdom

Device

Samsung Galaxy S23 Ultra

Operating System

Android 16, One UI 8.0

Spotify App version
9.1.24.1739

My Issue

When you start a playlist, etc and it adds songs to the queue, you are shown clear or edit, if you press edit and select the first song thats next in the queue and press move up, it just duplicates the song, not sure if that's intended or not since the song is already considered "Next up", so it will just play the song twice unless you remove one of them from the queue even when connected to other devices, i've attached a Video showing exactly what I mean, if you keep doing it to the first song it just keeps adding the same song to the queue, the Video doesn't show it entirely due to file size but I got to around 20 songs that are identical back to back in the queue.

Realistically if move up was selected it should either move the original place OR just not provide a move up button for the song in position 1 on the queue.

If this is supposed to be intended then "Move up" should be something else since the song is already at the top of the queue. for example: duplicate... I'm also pretty sure this would break the player if it kept being duplicated, but I have not tested that out yet because I just want to listen to my music.😅

Re: Move up feature in queue creates duplicates

Yordan — Mon, 23 Feb 2026 09:09:46 GMT

Hey, @Simply_Samps,

The intended behavior is for the songs to change their original position to the top without being duplicated.

Looks like the issue is isolated to Android. Thanks for the report - our tech folks will have a look. In the meantime. make sure to keep the app updated so you don't miss a thing.

Cheers 🤘

Re: Move up feature in queue creates duplicates

Novy — Wed, 29 Apr 2026 16:53:27 GMT

Hey @Simply_Samps,

Thanks for your patience while we looked into this.

Our teams have made some changes and this issue should be fixed, can you confirm if it's working correctly on your end now?

We'll be on the lookout.