Keybase login error code 202 on all devices.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
my log id: ebae9766b814f09ad636c01c
server rejected session; is your device revoked?
Error code 202: BAD_SESSION in method keybase.1.login.login
My chain and graph show no revoked devices.
Logging in via windows or android client both show the error 202 BAD_SESSION.
logging in via web-browser on keybase.io shows no errors in console or network responses, but it does nothing other than show the public part of my profile.
Also the profile icon on my profile is now blank, where it was previously an image.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reproducing the login.login failure with error 202 and reviewing the supplied log ID ebae9766b814f09ad636c01c. Done would require identifying why sessions are rejected and restoring login behavior across the reported clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100