iOS Client: "null is not an object" error message appearing in chat
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Using the Keybase iOS version, and I had this error message suddenly appearing in chat:
This seems to be JavaScript related.
The message appeared immediately after I went on the app (it was in running in background)
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 error in the Keybase iOS app after it has been running in the background, then investigate the JavaScript-related chat path indicated by the message. Done means the reported “null is not an object” message no longer appears when returning to the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100