element-hq / element-hq/element-call

Stuck on "Waiting for participants" but can hear other people

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

Description

### Steps to reproduce

Unknown

Seems the client managed to get itself into a state where it was stuck on 'waiting for participants' but it was joined to the livekit room, receiving media from other people and playing their audio. Rageshake shows, "tried to update participants before local room member is available" which implies the client has lost its own member event, presumably though state being corrupted / lost somewhere between synapse, js-sdk and js-sdk indexeddb storage.

### Outcome

#### What did you expect?

#### What happened instead?

### Operating system

_No response_

### Browser information

_No response_

### URL for webapp

_No response_

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Research direction

Start by searching for the rageshake message "tried to update participants before local room member is available" and trace participant updates across the client, Matrix JS SDK, IndexedDB state, and the LiveKit room. Reproduce or construct a state where media is received while the local member is missing; done means the client no longer remains on "Waiting for participants" in that state.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
audio-video-rtc, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.