Hi ​@Nerocris 

Thanks for your post!

Sorry to hear of this issue you are having with duplicates showing in the queue when adding a large YouTube Music playlist to it.

Thanks to a similar post linked below, a colleague recently tested this and found the same behaviour. We are investigating.

I hope this helps.

Hi ​@Nerocris 

I can confirm that we have identified an issue with multiple duplicates showing when adding larger playlists to the queue and are investigating. I have no estimate for when a fix might be put in place, but I will update this thread when I hear of one.

I hope this helps.

Good morning, with this problem the YouTube music playlist cannot be listened to as the same songs are typed over and over again. phono a10/15 days ago everything worked wonderfully. Is it possible that it's so complicated to find a solution? A thousand thanks

Hi ​@Nerocris 

Many lines of code will need to be sifted through to find what may be a single syntax error - it could just be the use of a semi-colon where a colon should have been used, or another typo of some kind.

I have no idea how long it will take to fix, but considering the scope (it is affecting more than just YouTube Music) I think it will be a priority.

I hope this helps.

Hello!

I’m having what I believe to be the same issue.  I believe that it’s a problem with the way the app retrieves and displays data from the YouTube Music API.  It repetitively loads the first 100 songs on a playlist into the Sonos app, instead of loading the entire playlist as you’d expect.  I suspect that it was originally designed and intended to retrieve and display 100 at a time and something broke.  Something looped back to the wrong command or something like that.

It used to be that whatever error was in there was corrected when the songs were loaded into the queue, so the entire playlist would cue up, play, loop, and shuffle properly, despite the playlist menu displaying only the first 100 repetitively and (I suspect) infinitely.  But now it appears that whatever tiny bit of programming was holding it barely together appears to have also broken.  Now I have the first 100 songs loaded up over and over again in the queue until it’s absurdly long.  The stopping point is usually somewhere in the neighborhood of 35,000 songs for me and it appears to be different every time.  Perhaps it stops when something times out or something runs out of memory.

The app ignores commands to delete the queue while it’s doing this.  The only way I have found to clear it is to load up a playlist less than 100 songs long to avoid triggering this bug, then delete the queue.

Notably, it appears that the queue can still handle over 100 songs correctly.  Loading them up individually, or from multiple shorter playlist under 100 songs each, still works fine.  I can also play long playlists fine on the YouTube Music app on my phone and connect it to any BlueTooth device, but not the Sonos system.   
 

Whatever is going on with our respective queues is most definitely a Sonos playlist problem, not a Sonos queue problem or a problem on YouTube/Google’s end.

I have been less than impressed with the Sonos backend and app experience since I started using my dad’s system earlier this year.  Things keep getting broken in the strangest ways.  Normally anything that prevents me from using the app the way I want is fixed within a week but this one has been active for way too long and getting worse.  It shouldn’t be that hard to load up 7 of my long playlists into the queue and get music ready for the whole weekend.

I’m running the latest version of the app on iOS 18.1.1 and an iPhone 11 

Good morning, I hope that what I am about to say helps programmers find a solution to this problem. I too, as I have already written, have the problem of 33,000 tracks loaded.

If I go to Sonos in the YouTube music/collection/playlist section and select my collection and press play, the system loads the 33,600 repeated tracks of my collection of only 217 tracks.

But if instead of pressing play I press the button with the three dots and then press the play now button, the error disappears and loads exactly my 217 tracks.

I kindly ask Sonos to commit to resolving the error because it is very unpleasant and does not allow you, if not with the expedient just described, to fully enjoy your tracks.

Thank you very much

That’s very interesting.  Your workaround works perfectly for me.

That’s where a code, test, release cycle works better than code, release, test cycle.