keybase / keybase/client

Keybase mobile client hang/freeze/lockup

Open
#10,255 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

This has happened several times, so logging it as an issue. On the Keybase iOS mobile client, I will often get an iOS notification that I have received a new keybase message. However, when I open the Keybase app to view it I am presented either with stale messages or with no messages at all. The only way I've found to correct this is to force quit the app and restart it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the notification flow in the Keybase iOS mobile client: open the app after receiving a new message and compare the displayed state before and after force quitting. Investigate why stale or missing messages appear, and consider the issue done when opening from a notification reliably shows the new message without restarting the app.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, react-native
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.