Music.YouTube won't move onto next song

Description of the issue:
When I listen to a playlist in in Music.YouTube.com the next song won’t play after the currently one finishes. Instead, it will play the same song over and over again.

Exact URL of the website in question:
https://music.youtube.com/watch?v=xkIytYlDD_o&list=PLN_Ufa_LlrdR6US4mkvIz92hbepMfQ0Qx

Did the issue present with default Shields settings? (yes/no)
yes

Does the site function as expected when Shields are turned off?
no

Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no):
no

Does the site work as expected when using Chrome?
yes

Brave version (check About Brave):
[Version 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)]

I have also added an exception to AutoPlay for https://music.youtube.com/watch?v*. to always allow, restarted Brave, and it still wouldn’t autoplay the next song.

Thanks @Barda4 for reporting. What OS are you on?

I am running Windows 10 Pro, Version 10.0.17763 Build 17763

Thanks @Barda4, I’m not able to reproduce on MacOS, it successfully moves on to the next song. @fanboynz would you be able to take a look?

Hey, I took at look at. I had no issues, the auto-play enabled. I played a few tunes and it kept playing through

Is there anything I can do to help debug? I can also re-install and take a video if that helps.

1 Like

Maybe a new profile? Could you try in Brave-beta (assuming its a new profile), without any extensions.

Using the Brave build [Version 1.1.5 Chromium: 78.0.3904.97 (Official Build) beta (64-bit)] I am seeing the auto-playing working.

Following your comment about a new profile. I opened a guest window in the Version 1.0.0 build, and the auto-play feature was working.

I then added a new profile to Version 1.0.0, loaded that profile, went to music.youtube.com and the auto-play feature works again.

I am cool to move on with using a new profile, but if there’s anything you guys would like me to take a look at or compare, feel ask!

Thank you guys for your time!

and now I can’t repro the problem when I switched back to the original profile, maybe something odd was cached that got cleared when I changed profiles?