Truncated Queue

[jbeejone]

Plan

Premium

Country

UK

Device

iPhone 11

Operating System

iOS 18.3.2

My Question or Issue

After the latest mobile UI update for how the queue displays, I noticed it truncated the queued songs after a certain point (the length of the visualised queue). For example, I queue up 3 albums, and the number of total songs goes over the amount that the queue menu can display. Instead of storing the other songs out of sight, it just cuts them out of the queue, and the next song would be whatever I was originally listening to. Have not checked on desktop. In the photo, you can see that the trial of the Chicago 7 soundtrack was cut off half way through, after adding the entire album in one go. 

[Ivelina]

Hey @jbeejone,

Thanks for posting this thread in the Community!

Maybe you wanted to attach a screenshot, but sadly we don't see it. Could you give it another try? You should be able to attach it to your next response via the Insert Image option in the post editor. It'd be great if we could take a look at how things look like from your end.

Additionally, let us know if this happens if you try to queue any other items and not albums and if you've performed any troubleshooting steps so far. I recommend a clean reinstall (if you've not already tested this) which often helps resolve different performance issues and includes steps to clear the cache.

Lastly, let us know if this happens if the playback is directly from your iPhone, or you're playing to an external device via Bluetooth/Connect (headphones, speaker etc.).

Don't hesitate to let us know if anything else comes up in the meantime. 

[jbeejone]

Hi, sorry about the image disappearing, should be uploaded now. I’ve manually cleared the cache, I’ve updated the app and done a clean install. After some more experimenting, if individual songs are added, they’ll get dumped from the queue if a previous song in the queue is removed from the queue. If a previous song is skipped, the queue continues, adding the not-seen-in-ui songs to the queue. The logic seems to be if the album exceeds the length of the viewable queue, the remaining part of the album is dumped, and if songs are removed from the queue, the excess queue is dropped. The only way for an excess queue song to go into the viewable queue is by either skipping or playing through the current song. I’m currently playing it on headphones, but the problem persists even direct from the phone. 

[Ivelina]

Thanks for the quick response and screenshot @jbeejone.

It's great that you've already performed some troubleshooting steps and we appreciate you sharing what you've tested with.

We'd like to take a further look into this behavior, so would you mind sending a video recording here of how the queue behaves? You can once again attach it to your response (Insert Video) or if the attachment's too big - then you can upload it to Google Drive and share the link with us.

It would also be helpful if you could include the exact Spotify-version you're using.

In the meantime, something else that comes to mind is to ask a relative or a friend to log in to their account on your iPhone to see if the same behavior would persist.

We'll be on the lookout.

[jbeejone]

Hi Ivelina,

Here’s the behaviour videos (sorry for the quality!) https://drive.google.com/file/d/1FjQThTaMaThghGGGOYFcp9ee9eB6verr/view?usp=drivesdk

https://drive.google.com/file/d/1NrIMHzcU8mIGI6SJ57G4FyDWI7-kGz9c/view?usp=drivesdk

The first one (Severance soundtrack) is showing the expected behaviour - you add a bunch of songs to the queue, and when one finishes, or you skip, the items from the excess queue get added to the queue. The second video (undertale soundtrack used), shows the unintended behaviour, where deleting a song from the queue dumps the excess queue. The excess queue doesn’t get dumped if you skip ahead multiple songs (e.g pick a song from the queue directly) and doesn’t get dumped if you search a new song, play that (overriding the current song choice). It also doesn’t dump the queue if an unavailable song is “next” in the queue (e.g. added whole album with unavailable songs) It does dump the excess queue if you rearrange songs in the queue. So my best guess is that any time the queue’s order is changed (deleting songs or rearranging them), the excess queue gets dumped by mistake. 

I’m running version 9.0.32.638, and I can’t get anyone else to test this at the moment, sorry!

Let me know if there’s anything else I can do to get this sorted!

[AlejaR]

Hey there @jbeejone,

Thanks for the videos, it helped us a lot.

We'd like to gather some additional info for us to continue investigating this behavior. We'd like to check:

• Does this happen on a different device, perhaps an Android mobile? If possible, you can ask for the device of a relative or a friend to open your account there and check.
• Does this happen when you queue for specific albums? Or does it happen just when you alter the queued order?
• Did you notice if this started to happen after a specific event such as an OS update?

It'd be awesome if you could check if the same happens on the desktop app, so we can continue isolating these issues.

Keep us in the loop!

[jbeejone]

Hi Aleja,

I’ve now confirmed that the issue is present on other accounts on other devices. The issue happens regardless of the queue content, I’ve tried it with various albums and just queuing up individual songs - same situation. The issue began after the update to the queue UI (don’t know the exact version number) - when it changed from a separate view to a tab contained in the “now playing” screen, and then had album icons. The bug is also present on the desktop version, running the latest version on windows. Exact same issue - tampering with the queue in anyway will drop the excess queue. This also wasn’t seen on desktop prior to the queue UI overhaul. Let me know if there’s anymore information I can provide!

[AlejaR]

Hey @jbeejone,

Thanks for all the info you kindly sent to us.

We could replicate this behavior on our side. We've gone ahead and passed this info to the right team, so they can continue investigating. 

Meanwhile, we suggest you subscribe to this thread in its three-dot menu. That way, you’ll be notified as soon as we get news to share.

We'll be around, so don't hesitate to let us know if you have further questions!

[davean_52]

Plan

Premium

Country

United States

Device

iPhone 16

Operating System

iOS 18.3.2

My Question or Issue

For the past handful of months (not exactly sure how long, sorry) I’ve had an issue with queueing up a bunch of songs where a certain amount of them will play, then a huge chunk of them gets skipped, and then it resumes playing what I queued way down the list (Ex. if I queue 50 songs, 1-25 will play, 26–40 will not, and then 41-50 will play). I know for a fact that I used to be able to queue up hours worth of songs while working so that I wouldn’t have to keep taking out my phone, and this skipping was not an issue.

On top of this, for some reason, when I queue up a bunch of songs, there seems to be a cutoff of the amount of queued songs I can view, which I also know didn’t used to always be the case.

[Joan]

Hi there @davean_52,

Thanks for reaching out. We'll be glad to help you get the queue working as expected again.

This is quite odd and we haven't seen reports about this exact issue. Does it happen regardless of where you're queuing the songs from - playlists, liked songs, albums, etc.? Test out if this happens on different networks and in offline mode. In any case, also perform a full clean reinstall if you haven't already as that can resolve a multitude of issues and hopefully this is one of them too.

Let us know how it goes.

[davean_52]

Hi Joan,

Thank you for getting back to me. To answer your questions, yes, this happens regardless of where I am queueing from. Most of the time, I am queueing up full albums, but sometimes I am also queuing individual songs I want to listen to from some albums.

Unfortunately, nothing has changed after following the clean reinstall procedure. I just tested it out again and the issue persists. I will detail what I did below to make the predicament clear:

I queued up 13 albums in a row for a total of 219 tracks that should all play one after another. When viewing my queue, I can only see the first 5 albums before it hits the bottom, and I can no longer scroll, with the last two songs of the 5th album not being visible. This totaled to 80 visible tracks in my queue.

When I skipped for the first time, I expected the next track from the 5th album to appear at the bottom of the queue, but instead, this is where the main issue comes in. Albums 6-12, along with those last two tracks from album 5, have been COMPLETELY skipped (125 tracks skipped), and, instead, the next song that appears at the bottom of the queue is track 1 from album 13, the LAST album that I queued. Then, as I continued to skip, all 14 tracks from album 13 continued to fill out the queue as I'd expect.

In other words, out of 219 queued songs, 1-80 appeared and played as expected, songs 81-205 were skipped, and then the queue resumed for the final 206-219.

[Joan]

Hi @davean_52,

Thank you very much for the detailed reply.

This behaviour seem to match what's described in this bigger thread, so we've gone ahead and merged our conversation here to keep everything in one place. The issue is something we're already investigating so please try the troubleshooting provided thus far and send us any requested info. If you find anything new related to this issue, feel free to share it.

We'll keep you posted with updates if and when we have them in the meantime.

Cheers!

[Novy]

Hey everyone, 

Thanks for your patience while we looked into this. 

We've heard from our teams, and this seems to be an expected behavior at the moment. 

We appreciate all your feedback, which has been passed on to the relevant folks. The Community will be here if anything else comes up.

[jbeejone]

Wait, so this is expected behaviour as in it’s a bug that is logged and on the list, or the team is saying that this is the desired queue behaviour? Because if this is intended, what’s the logic behind it?

[jbeejone]

@Novy any update on this?