element-hq / element-hq/element-call
Got error while on an Element Call
- Dominant language
- TypeScript
- Stars
- 996
- Forks
- 213
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 54
Description
### Steps to reproduce
1. I was on an Element Call
2. All of a sudden after 30-40 odd minutes, I saw a red alert icon next to the video icon in the room list
3. I was raising my hand at that time, and was unable to un-raise it
4. I was unable to send messages in the room, I got the 'unable to send' error
5. After a while, the raise hand state went away on it's own
6. On ending the call, the error state went away
### Outcome
#### What did you expect?
No error state?
#### What happened instead?
### Operating system
macOS
### Application version
Element Nightly version: 2026011601
### How did you install the app?
_No response_
### Homeserver
matrix.org
### Will you send logs?
Yes
Contributor guide
Research direction
Start by reproducing the failure in an Element Call on macOS with Element Nightly version 2026011601, using the reported sequence of a call lasting 30–40 minutes. Review the promised logs alongside the red room-list alert, stuck raise-hand state, and unable-to-send errors; done means identifying the cause and verifying that these error states recover without ending the call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100