-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{'Error': 'BadAuthentication'} #24
Comments
There's not much to go off of. Maybe there's some more information in the response? eg #23 (comment) |
I've tried this with 2 accounts and I'm getting BadAuth every time. is there something specfic I need to do on my account to get this work? |
There's some details on what gmusicapi uses for device ids here. Ideally you'd reuse a real one that's already been attached to your account. |
I'm using mac address of my laptop which is trusted by google in my account. However I still getting {'Error': 'BadAuthentication'}. |
I'm not sure mac addresses work anymore. You might have to try a random android or ios id. |
I've got android_id of my phone, same problem :( should this work without app password and 2fa disabled? |
Yup, it worked for me earlier today. |
is there anything else I have to do to get this work besides valid android_id and disabling 2fa ? |
There shouldn't be. Did you try an ios id? |
how can I get ios id from my iphone? I just tried with my boyfriend's account. it does not work either. |
same with ios :(
|
@simon-weber could you please look at the code? it does not work with 4 different accounts. I don't think it's something related to the account. |
That code looks fine to me, and gpsoauth itself hasn't changed in a while. If there's no issues with the input or accounts, then it sounds like something changed on Google's end. What are you trying to accomplish with gpsoauth? Will a normal oauth flow (even one that reuses another app's client credentials) work instead? |
no, oauth won't help at this point because I'm trying to use google keep's unofficial API gkeeapi. I still can't understand why it's working with your accounts and not with mine :/ |
[this was directed at another user that I think GitHub auto-blocked, since an earlier redacted comment is now gone:] Can you share your solution here, please? I've edited out your contact information in the meantime, since I don't want to encourage people to reach out directly to someone unrelated to the project, especially when it may involve Google SSO credentials. |
I did not see the comment, was there any solution? |
No, I'm pretty sure they were some kind of scammer. |
Did you figure this out @alils ? I'm running into the same issue. |
I'm running into the same problem. Tried different account and different combinations (2FA enable/disabled, plain text password, app password...) |
I also had this issue on Raspberry Pi running Python 3.5.3. For some reason, when I ran it on a Windows machine it worked. Both in Windows Subsystem for Linux and Windows. Python 3.8.5/3.8.6. Upgraded the Pi to Python 3.9.0 but issue persists. Guess I'll just run it on Windows. |
Hey, I was experimenting with different Python versions (see here: rithvikvibhu/GHLocalApi#54) and for me it suddenly started working on |
I haven't tested this, but I got an email from someone who claims downgrading requests fixed this for them: version 2.25.1 didn't work, but 2.23.0 did. They're on python 3.7.7 on windows. |
Quick question, what do you mean with "downgrading requests" ? |
I'm referring to requests, which is a dependency of gpsoauth. ie, try |
Looking at a diff of v2.23.0 - v2.25.1, this change seems suspect. Might take a closer look at this if I've time. |
@simon-weber FWIW it started working for me after downgrading from |
Haha, yeah, I don't know what's going on either. If someone can pin down the problem or which versions definitely do and don't work I can change the package requirements. I'm hesitant to mess with it, especially now that pip is more aggressive about conflicts. |
I was in the process of bisecting to find what broke it – but now I can't 'cause it's working :-\ |
Same here. |
Hm. Well, it's always possible we're dealing with something weird on Google's end. Maybe they have automated systems to block user agents; I think those depend on both the python version and the requests version. |
I have the exact same problem, downgrading and upgrading again solves the issue. Can it be that a dependency bundled with 2.25.1 (when you first installs it) creates a weird problem with how google handles the login but when you downgrade and then upgrade again it only upgrades some of the packages because only som og them ære required to be new, but others are allowed to be older (but newer ones are installed the first time) I have this problem on Homeassistant in docker on an Arm/Alpine image (stock image for Homeassistant) |
Could be! What's the diff in packages between the downgrade/upgrades? |
See this log. urlib3 is downgraded but not upgraded again If there is a better way to include this log info below, please let me know. Im new to github `bash-5.0# pip install requests==2.24.0 We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default. samsungtvws 1.4.0 requires websocket-client==0.56.0, but you'll have websocket-client 0.54.0 which is incompatible. We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default. synologydsm-api 1.0.1 requires requests<3.0.0,>=2.24.0, but you'll have requests 2.23.0 which is incompatible. |
Nice find. My diff of
So, if someone's got a repro of the problem, maybe try downgrading chardet and then urllib individually to see if either of those alone fix it. |
A quick test showed me that if urllib3 is larger then 1.25.11 it will fail with They made a couple of changes to how urllib3 works in 1.26.0 see: urllib3 |
Yup, it looks like that's it! It seems like some unknown interaction between some new urllib3 options and Google: urllib3/urllib3#2101. It doesn't look like there's any workaround right now, so I guess I should just disallow urllib3>1.25.11 for now. |
We can only hope that Google fixes it on there end at some point Have a nice day |
I keep getting "{'Error': 'BadAuthentication'}" with either account password with 2factor authentication disabled and app password with 2fa enabled.
The text was updated successfully, but these errors were encountered: