Google-play-music-desktop-player-unofficial-: Login Issues

[betmakh]

Checklist:

• [x] I have checked that there are no issues with similar or the same content

  YOU SHOULD CHECK CLOSED ISSUES ASWELL

• [x] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there
• [x] I have double checked and can reproduce the issue

*OS: MAC OS Catalina 10.15.1 *

GPMDP Version: 4.6.1

Issue Descriptions: Can't login any more

**Steps to Reproduce:

1. Delete your data folder ~/Library/Application Support/Google Play Music Desktop Player. I did it because got stucked on Loading your library screen)
2. Open app and try to login
3. Login fails with info that my browser is not secure for logging in:

Couldn't sign you in

You are trying to sign in from a browser or app that doesn't allow us to keep your account secure.

Try using a different browser. Learn more

P.S. I tried to disable 2 factor auth for the google account but it didn't help
debug_info.zip

[welcome[bot]]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of duplicate issues on this repo, so please double check now that your issue has not already been solved or doesn't have an open issue already.
To help make it easier for us to investigate your issue, please follow the contributing guidelines and ensure the issue template was filled out.

[Mallox51]

Same problem for me here, with macOS 10.15.1 Catalina
I'm stuck on

• tried to delete my ~/Library/Application Support/Google Play Music Desktop Player directory.
• Logged me in again
• Stuck on the same screen again

UPDATE :
Ok maybe this thread is a duplicate of my problem : https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/3660

For lazy OS X users: https://3667-40008106-gh.circle-artifacts.com/0/home/circleci/project/dist/installers/darwin/Google%20Play%20Music%20Desktop%20Player.zip
May become dead in the future, I don't know how long Circle retains artifacts.

[rijnhard]

same here But Linux Mint 19

[conradfr]

The CI build fix the splashscreen hang but I can't use the scrollbar (mouse wheel works).

[rembk4y]

Confirm, same problem here, Linux Mint 19.2

[JeffLCoughlin]

Same for me on Mint 19.2 and RHEL 7

[kroppt]

Also a problem on Windows 10

[chasfh]

Windows 7 also. I have uninstalled for the time being.

[AntonioMichaelAlvarez]

Same, Xubuntu 16.04.6 LTS, GPMDP 4.6.1 Debian 64-bit *.deb

[danryandesigns]

Couldn't sign you in
You are trying to sign in from a browser or app that doesn't allow us to keep your account secure.
Try using a different browser. Learn more

Same issue. Windows 10.

[8simsim8]

Confirm, same problem: macOS 10.15.1 Catalina

[jostrander]

I am closing this in favor of the pinned #3545. It appears to be now effecting more of you now that we are closer to the end of the year deadline that Google was imposing, but in theory is fixed in the next release.

[betmakh]

I am closing this in favor of the pinned #3545. It appears to be now effecting more of you now that we are closer to the end of the year deadline that Google was imposing, but in theory is fixed in the next release.

Hi @jostrander I checked the thread and pr. I also pulled the code change which should fix the issue and rebuilt project locally but it does not fix the issue.

After checking the project's code and electron docs: https://electronjs.org/docs/api/webview-tag I think the issue here is that app uses tag to authorize user. Which can mean project's architecture needs to be changed to use google libs to auth user instead.

I think the Issue should remain open

Thanks

[jostrander]

@betmakh The issue is indeed that the application uses the web view tag. Unfortunately there is no other way for us to integrate with GPM and YTM as far as authentication goes. We are simply injecting functionality into the existing web apps that Google provides via the web frame.

I'm not sure why the latest changes didn't fix the issue for you, unless Google has changed the way they check for third party "browsers" again. Either way it should be tracked in the existing issue, IMO.

[aachowhan]

Same issue on Windows 10.

[Recif2]

Same issue here (Windows 10 / Chrome 78.0.3904.108

[mojhale]

I found a solution to the same issue for me with this post on the related thread linked above.