Android app - eldest called on user with existing eldest KID
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This may be a duplicate of #6962
Steps:
- Fresh install/new user (account created via web, no other devices used)
- Log it, get to the paper key screen
- Lock the screen
- Unlock
Now you're back at the main screen and the paper key gone. I was expecting that since there is a switch to confirm that I wrote down the key all will be fine.
- Revoke the paper key
- Revoke the device
- Log in: "eldest called on user with existing eldest KID"
Removing app data does not help, neither does reinstalling.
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 by reproducing the fresh-install flow through the paper key screen, screen lock, paper-key revocation, device revocation, and subsequent login. Compare the behavior and discussion with issue #6962; done means the described login error is resolved and the paper-key confirmation state remains consistent after unlocking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100