New login issue (Was working fine for months)
See original GitHub issueThe issue
I’ve been using this code successfully for the past few months (thank you!) and then it suddenly stopped working. I am getting the error posted below. I am wondering if this is the result of security changes at Google? Or what I am overlooking in my attempt to debug.
My attempts at solving
- Two factor turned on
- App pass created using this link: https://myaccount.google.com/apppasswords … then I copy and paste that pass into the sample code below.
- Running recent version of Python3 (3.8) and receive same error on local dev and remote
- Manually unlocked captcha using following link and have tried this many times UnlockCaptcha manually
- I am logged into GoogleKeeo in my browser.
I tried turning off two-factor and reseting and then creating a new app pass but that produced same error. Again, any help is appreciated as I depend on this for my workflow.
Error
File "/Users/Me/Projects/gkeep/test.py", line 4, in <module> success = keep.login('me@gmail.com', 'apppassword') File "/usr/local/lib/python3.9/site-packages/gkeepapi/__init__.py", line 695, in login ret = auth.login(username, password, device_id) File "/usr/local/lib/python3.9/site-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.')
Running this code
`import gkeepapi
keep = gkeepapi.Keep() success = keep.login(‘myemail@gmail.com’, ‘workingapppasswork’)
note = keep.createNote(‘Todo’, ‘Eat breakfast’) note.pinned = True note.color = gkeepapi.node.ColorValue.Red keep.sync()`
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:33 (7 by maintainers)
Top GitHub Comments
New Release and Commit that fixes the issue
I’ll try to update the dependency manually and see if it fixes the issue
Update: I currently have a functioning python3 env, my
pip
broke. I have to figure out what happend there first. Maybe someone else can check if the new version ofgpsoauth
worksThanks for testing. I’ve bumped the dependency on
gpsoauth
to1.0.2
and published0.14.0
, which should fix the issue.