Skip to main content
Answered

YouTube music auto play next song

  • February 13, 2025
  • 2 replies
  • 238 views
T

Hi, I have only just started using Sonos / YouTube music however have come across a difference in functionality between Android and iOS devices.

 

In the Sonos app, if I navigate to YouTube Music > Library > Songs and select a song to play, it plays that song as expected. The difference is, that on iOS (both iPhone 16 Pro Max and iPad Pro), it ONLY plays that one song and stops, however on Android it continues to work it’s way down the song list automatically which is what I would expect. Is there a setting to enable “next” to play in iOS?

 

In iOS, a PLAYLIST continues with the next song as expected as does in Android.

Best answer by Corry P

Hi ​@tb123 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with playing more than one song on YouTube Music from an iOS controller.

We are aware of this issue and are investigating, though we do not have an estimate for when a fix might be in place. There is no setting you can change, but hopefully we’ll see the expected behaviour soon.

I hope this helps.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

2 replies

Corry P
Forum|alt.badge.img+19
  • Corry P
  • Sonos Staff
  • Answer
  • February 13, 2025

Hi ​@tb123 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with playing more than one song on YouTube Music from an iOS controller.

We are aware of this issue and are investigating, though we do not have an estimate for when a fix might be in place. There is no setting you can change, but hopefully we’ll see the expected behaviour soon.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
    T
    • tb123
    • Author
    • Contributor II
    • February 13, 2025

    Hi, thanks for the reply and confirming that this is not expected behaviour, I’ll wait for the fix, cheers

      Terms & ConditionsCookie settingsAccessibility statement