search

stevenleeg / geemusic

A bridge between Google Music and Amazon's Alexa
GNU General Public License v3.0
662 stars 178 forks source link

Tried all "Login unseccessfull" solution but still stuck on this error #268

Closed mrecamales closed 5 years ago

mrecamales commented 6 years ago

I have followed the steps of the Heroku part, with a Google account with 2FA, generating an app password, and used this password in the GOOGLE_PASSWORD field. image (I have replaced all the values with '*' just for the screenshot, but they are all set correctly).

But there's still the same error:

image

I should mention that my Google Music account is a free account, but I have uploaded a couple of songs. I'm a very beginner on this (I beg you patience), may I modify the code or something?

coggy9 commented 6 years ago

I'm having this issue with a paid account. Might be Google blocking Heroku logins, as I had this warning in my Google account after I tried to login a few times.

mrecamales commented 6 years ago

I've received the account warning too, but I thought it was not supposed to happen if you have a 2FA and an app password created

coggy9 commented 6 years ago

I got it to work by using this page, and letting the app retry the login a few times.

fergyfresh commented 5 years ago

Yeah. there is a known bug in the upstream repo https://github.com/simon-weber/gmusicapi/issues/620. He has a fix on a dev branch and i'm going to roll it in to this once he irons it out or when I get around to it, whichever comes first.

fergyfresh commented 5 years ago

I got another implementation working on the develop branch. If you wanna try it out over there @coggy9

gmarblestone commented 5 years ago

@fergyfresh i got an error No module named 'fuzzywuzzy' on Heroku

fergyfresh commented 5 years ago

what branch?

gmarblestone commented 5 years ago

@fergyfresh develop

fergyfresh commented 5 years ago

you are right. i messed up, the fix is out git pull origin develop.

gmarblestone commented 5 years ago

@fergyfresh thanks... ill check it out

gmarblestone commented 5 years ago

@fergyfresh hate to bother, but getting another error running now. Thoughts on DEVICE_ID?

2018-12-06T22:00:47.454657+00:00 app[web.1]: return cls(os.environ['DEVICE_ID'], 2018-12-06T22:00:47.454659+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/os.py", line 669, in getitem 2018-12-06T22:00:47.454999+00:00 app[web.1]: raise KeyError(key) from None 2018-12-06T22:00:47.455006+00:00 app[web.1]: KeyError: 'DEVICE_ID'

fergyfresh commented 5 years ago

Read the read me. you gotta run some commands first and put them in the device id.

gmarblestone commented 5 years ago

@fergyfresh my fault, you're right i didn't read. So i was able to run the two python commands and the return was gmusicapi.exceptions.InvalidDeviceId: Invalid device_id .Your valid device IDs are:

So, i made a env = DEVICE_ID=A02F50D4-5632-41BD-A0CF-xxxxxxxxx

I still failed to authenticate... Any thoughts? did i use the correct device id?

Thanks again

fergyfresh commented 5 years ago

If I remember correctly theres something about device IDs in ios that you have to replace. I know that removing ios like you did is one of the steps. Maybe there is another step associated with removing dashes or something? Can any IOS users verify? @digiltd or anyone else? Look around for ios on open andclosed issues both here and at https://github.com/simon-weber/gmusicapi/ and see if you can drum up any info.