View Issue Details

IDProjectCategoryView StatusLast Update
0021146MMW 5Otherpublic2024-08-16 17:29
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Product Version5.1 
Target Version5.1.1 
Summary0021146: YouTube playback fails: "Sign in to confirm that you're not a bot"
DescriptionI just tried out YouTube playback and it prompted me to 'Sign in to confirm that you're not a bot'. However:
- it's not obvious how to sign in
- even if the user figures out how to sign in, it doesn't work due to 0021031

Here are the steps I took and a full explanation of the issue:

1 Minimize to miniplayer (this may not be relevant)
2 Click 'Next' to initiate playback of a track from YouTube
--> New window opens with the message "Sign in to confirm that you're not a bot", however, there's no sign-in link! So the user is forced to go through the following unintuitive steps 3-5
. 3 Right-click 'Web' > Add bookmark
. 4 Enter URL/Title: https://www.youtube.com / YouTube
. 5 Click YouTube
6 Click 'Sign in' and enter <username>
--> "This browser or app may not be secure" (bug 0021031)
7 Restore to the regular window
8 Play a YouTube track --> It fails!

Because of this change, YouTube functionality no longer works!
 
TagsNo tags attached.
Fixed in build

Relationships

related to 0021031 resolvedrusty Adding YouTube Music as Bookmark in Web node triggers 'browser deprecated' error in Title and login fails 

Activities

rusty

2024-08-16 16:21

administrator   ~0076660

Last edited: 2024-08-16 16:26

I just restarted MediaMonkey, and tried playing a YouTube track with MM running as a regular Window, and playback worked! So it seems that the issue may have been triggered by initiating YouTube playback via the MiniPlayer.

HOWEVER, when I tried doing so, the issue didn't occur this time! So I'm not sure why this occurred the first time.

Note: I've been testing while using a VPN--so it could be that the VPN triggered a flag in Google's login system.

rusty

2024-08-16 16:28

administrator   ~0076661

Last edited: 2024-08-16 16:30

Given that this is likely related to VPN usage, I'm pushing this for now to 5.1.1, to be retriaged post-release (I'm not closing it yet because there may be other cases in which this issue occurs).