Issues while adding a new device
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When adding a new device, the service looks for other devices added earlier so that it can engage in some sort of rekeying. The service fails to see existing devices that are only which requires that you enter a paper key. On entering the paper key, it is not accept in the client UI unless one adds an extra carriage return at the end of the form.
Thus, there appears to be one problem with seeing existing devices and another UI problem on parsing the text in the input form for the paper key.
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 new-device flow in the service and client UI, focusing on device discovery and paper-key input parsing. Done means existing devices are detected during rekeying and a paper key is accepted without an extra carriage return.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, react-native
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100