Unable to login

[stevearc]

Unable to login

[stevearc]

This sounds like a google auth problem; I'm not sure if there's anything we can do about it from the gkeep side. From searching around, you can try clearing your browser cookies or marking the urls as trusted. You could also try using a different browser, or you could try opening the devtools to see if there are any errors that contain clues. If you have 2-factor enabled, you could try temporarily disabling it, or you could try enabling it if you're not using it.

[kaizerx31]

I am facing the same issue

[WBuddhi]

I found the solution for this, follow this

[kaizerx31]

Thanks it works now

[stevearc]

Glad to hear it! I'm going to close this and pin it so it's easy to find if others encounter the same problem.

[srbhp]

I get this error

Unknown error logging in; please report an issue on github. API error: ('BadAuthentication', None)

But this Python script worked for me

import gkeepapi

keep = gkeepapi.Keep()
success = keep.login('[email protected]', 'APP-Passward')
print("######    TO DO             ################################")
gnotes = keep.all()
for ig in gnotes:
    if ig.pinned:
        print(ig.title)
        print(ig.text)
print("############################################################")


`:checkhealth gkeep`
Gives me 

`## Python 3 provider (optional)
  - INFO: Using: g:python3_host_prog = "/usr/bin/python3.9"
  - INFO: Executable: /usr/bin/python3.9
  - INFO: Python version: 3.9.6
  - INFO: pynvim version: 0.4.3
  - OK: Latest pynvim is installed.
`

I suspect gkeep.nvim somehow picks up an older version of python. 
How do I debug it ? 

[stevearc]

This is unrelated to the original issue, so I have filed a new one for you and moved the discussion over there

[kaddkaka]

Even though I use an App Password that I just generated I get this error when trying :GkeepLogin:
Failed to log in: incorrect password

The problem is with both my regular password, and if I disable 2 factor authentication. What do I do?

[stevearc]

@kaddkaka please file a new issue using the bug report template. This is unrelated to the original report here.