Can't provision new devices
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I've added one device, but I can't provision additional devices, either desktop or mobile. The GUI interface just shows "Device provisioning failed because this device went offline," despite this not being the case. Similarly, the command-line interface shows:
Enter the verification code from your other device here. To get
a verification code, run 'keybase login' on your other device.
Verification code: <removed>
- ERROR {-} Error in transport: msgpack decode error [pos 0]: API network error: doRetry failed, attempts: 5, timeout 10s, last err: context deadline exceeded
OK Verification code received.
- ERROR {-} Error in transport: msgpack decode error [pos 0]: API network error: doRetry failed, attempts: 5, timeout 10s, last err: context deadline exceeded
- ERROR API network error: doRetry failed, attempts: 5, timeout 5s, last err: context deadline exceeded (code 1601)
my log id: 4617792a5b4cee13ac0a8a1c
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
Reproduce device provisioning through both the GUI and command-line interface, using log id 4617792a5b4cee13ac0a8a1c and the displayed transport timeout. Start with the keybase login verification-code flow; done means additional desktop and mobile devices provision successfully without the offline or API network errors.
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
- 25/100