WIP: Allow Google Signin #508
No reviewers
Labels
No labels
awaiting-reply
breaking changes
bug
cannot-reproduce
dependencies
documentation
duplicate
electron-issue
enhancement
fix-available
good first issue
help wanted
invalid
javascript
need more information
need rebase
official-youtube-music-issue
plugin request
question
release
security
stale
Status: blocked
typo
wontfix
ytmd-issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: YTMD/youtube-music#508
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "linux-useragent-patch-2021-12-2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This doesn't truely fix the problem. A weird combination of refreshing several times and...generally spastastic navigation behavior seems to get around the signin. This is mostly here to show what I tried.
Related to #507
Gets weirder:
So after doing the weird navigation dance it kinda...doesn't sign in correctly. It appears if you are, but you get a signed out front page. Removing the patch, signing in, then signing back in by clicking your signed out account it works.
Obviously this is broken.
More testing and trying to find a concise path to it working finds it's just a coinflip. Trying going back, forward, and several other navigations seems to be random when it'll just work or not. So I'm stumped.
I also tried just updating the user agent but no dice.
Hello!
So I'm facing the same issue on Fedora using appimage. Just in case this info would help, I could not sign in to google account on Vivaldi until I turned on google's crypto token extension in privacy settings.
Cheers!
P.S.
Navigating back two times and forwards two times got me further trough login process. Good workaround, thanks )
Hey could you try my PR? #515
I think I might have fixed the problem 🙂
@WhiteHusky #515 was merged and should have fixed the problem
So this PR could be closed
Closing as it should be fixed and the PR is stale - feel free to re-open a PR if needed!
Pull request closed