BUG: server rejected session; is your device revoked?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Trying to log into an updated (restored from backup) iPhone 14 Pro iOS 16.4.1—and am met with error (in title).
The error message I am getting:
Error code 202: BAD_SESSION in method keybase.1.login.login
it started last week when I couldn’t see any of the messages in the teams I am in. I then reinstalled app to see if that would have resolved and now I am locked out of my device. I can’t use my paper codes nor can I use the “previous” device as it’s the same one as the one I am using.
Please advise.
Thank you for all your hard work, devs. Keep up the good work!
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
Start at the keybase.1.login.login entry point and reproduce Error code 202: BAD_SESSION with the restored iPhone 14 Pro on iOS 16.4.1 described here. Trace the session and device-revocation flow, then verify the behavior after reinstall, including paper codes and the previous-device path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100