[Keybase iOS v1.0.2] Unknown error: bad signature: non-canonlical [sic] JSON found in strict mode
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This error occurred in the Keybase iOS app after submitting the name of my newly added device during initial setup. All prior steps including scanning the QR code generated by another device running Keybase appeared to complete without error.
I have a screenshot of the error JSON output provided by the iOS app and am happy to provide it if it does not contain private information and would be useful, or else to redact any key pieces of data before submission for review. And as always, please let me know what other information I can provide to help debug!
For myself personally, this is not a high-urgency fix as I don't use Keybase too often and mostly use it on desktop (macOS) when I do.
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 initial Keybase iOS setup flow: scan a QR code from another device, submit the new device name, and capture the full error JSON, redacting private data as needed. Compare the failing strict-mode signature response with a successful setup; done means the device can be added without the non-canonical JSON error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100