Add automatic reconnection logic
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Issue
If WebSocket drops, the app stops working with no recovery mechanism.
Current Problem
- Connection drops → user can't talk anymore
- No automatic retry
- User must close and reopen app
- No visual indication of reconnection attempts
Desired Behavior
- Detect WebSocket disconnection
- Automatically attempt reconnection (with exponential backoff)
- Show user that reconnection is in progress
- Implement max retry attempts to avoid battery drain
- After max retries, show error and stop listening
Implementation Details
- Exponential backoff: 1s, 2s, 4s, 8s, 16s (max)
- Max 5 retry attempts
- Update connection status during retries
- Log each reconnection attempt
Contributor guide
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 locating the WebSocket connection handling and the connection-status UI in the TypeScript app. Test a dropped connection, then verify exponential retries at 1s through 16s, a five-attempt limit, status updates, logging, and a final error state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- mobile-dev, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100