Last year, YouTube removed the repeat button from its interface. For all users, the repeat button was greyed out when cast on their devices. Reportedly, the feature is making a comeback after a year-long hiatus. According to the latest report by 9To5Google, YouTube Music is getting back the repeat button, and it is no longer greyed out when casting. Notably, the feature seems to be up and running on Android and iOS devices. However, sadly, it is still not available on YouTube Music’s iPad app. The function to shuffle and repeat started appearing on the YouTube Music app, back in February 2021. Later, both features were pulled back from the app, although there were no noticeable issues with either function. A month later, the shuffle feature was brought back, but the repeat button wasn’t available. The people who loved the repeat button on their YouTube Music app will be happy to learn that the feature is now live.
The repeat button shows up a few seconds after the casting is started
As noted by 9To5Google, the repeat button does not show up immediately and remains greyed out, but after a few seconds into the casting, the repeat button becomes fully functional. Thanks to this feature, you can now repeat a song, an album, or even a playlist when casting your Android device to a Nest Hub or a smart TV. It remains to be seen whether the feature’s rollout was a fluke or if it is part of Google’s A/B testing and is here to stay. Users now have the ease of repeating songs or albums, which previously required the manual addition of tracks several times to the queue or making a temporary list. If you have started seeing this new Repeat button on your YouTube Music app interface when casting, then you are all set. For those who aren’t seeing the repeat button, we would advise you to download the latest update of the app. For that, simply head over to the Google Play Store, see the update app section, and install the latest update if available. There is no surety if this feature will go live after installing the latest update, as it seems to be appearing after a server-side push.
