element-hq / element-hq/element-call

Network changes are slow and take ~30s to be picked up

Open
#1,612 0 comments 0 reactions 0 assignees View on GitHub
T-Defect
Dominant language
TypeScript
Stars
996
Forks
213
Avg merge
1d 6h
Merged PRs (30d)
54

Description

### Steps to reproduce

1. Start a call on wifi on iOS
2. Switch off wifi to fall back to 5G because you're leaving the building
3. Observe the transition takes ~30s to complete.

### Outcome

#### What did you expect?

~10s (or less) to notice that you've switched network and reconnect - which is what Jitsi manages.

#### What happened instead?

30s, which is very painful

### Operating system

_No response_

### Browser information

_No response_

### URL for webapp

call.element.io

### Will you send logs?

No

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the transition on call.element.io using the reported iOS Wi-Fi-to-5G steps and measure how long network changes take to trigger reconnection. Compare the observed delay with the expected 10 seconds or less; done means the call reconnects within that target after switching networks.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, typescript
Domain
audio-video-rtc, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.