Closed wizpig64 closed 3 years ago
Is there a reason this couldn't use the server sdks?
@vitriolix The Keep API is private, so there's no way to get valid API tokens for it via public mechanisms.
gpsoauth
uses the login flow that Google Play Services uses, which (I think) is unique from the CEF flow. That said, there isn't much that can be done right now, so we'll just need to see what happens on Jan 4.
Sigh....why don't they just release an official Google Keep API???
so the below would be due to this change? Just found this project and sigh THIS:
keep.login('############@gmail.com','****') Traceback (most recent call last): File "
", line 1, in File "/usr/local/lib/python3.8/dist-packages/gkeepapi/init.py", line 695, in login ret = auth.login(username, password, device_id) File "/usr/local/lib/python3.8/dist-packages/gkeepapi/init.py", line 59, in login raise exception.LoginException( gkeepapi.exception.LoginException: ('NeedsBrowser', 'To access your account, you must sign in on the web. Touch Next to start browser sign-in.')
Login still works for me today. Not sure which one is more odd: the error above or that it's still working. Note: I don't have 2FA enabled.
I am an idiot. More an infrastructure guy than python. I had to generate an app password for it to work.
if you're an idiot, you're a helpful idiot. i'm closing this issue, because logging in still works, and it's after January 4th.
thank you! :)
from https://developers.googleblog.com/2020/08/guidance-for-our-effort-to-block-less-secure-browser-and-apps.html via https://news.ycombinator.com/item?id=25172755
It looks like google is going to block signing in with usernames/passwords through tools that aren't officially trusted browsers. This could affect how gkeepapi obtains master tokens.
I'm not 100% sure how gkeepapi's login system works, but it sounds like it might have to change to use "browser-based OAuth 2.0 flows".