Unable to authorize a new Windows 10 device using my phone
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm setting up Keybase on a new Windows 10 machine. When I select my Android phone to use as verification, once I name the new device, Keybase crashes, as captured in the attached log ID. When I select a Linux computer (my only other machine) instead, Keybase does not crash, and I am able to add the device properly.
Log ID: 7799345c8da435920e12221c
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 with the attached log identified by 7799345c8da435920e12221c and reproduce device authorization on a new Windows 10 machine using an Android phone. Compare that path with authorization through the Linux computer, where the device is added successfully. Done means the Windows authorization flow no longer crashes and the new device is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go
- Domain
- authentication, desktop, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100