When clicking on a room while in an element call the call sometimes disconnects
Steps to reproduce
- Join an element call video room
- Click on another room (e.g. a text room)
- Get disconnected from the call
- When rejoining, I can't hear the other call members until they all reconnect
Outcome
What did you expect?
The call goes on like it normally does
What happened instead?
The call got disconnected
Operating system
Windows 10
Application version
Version von Element Nightly: 0.0.1-nightly.2024022701 Krypto-Version: Olm 3.2.15
How did you install the app?
https://element.io/download (nightly)
Homeserver
matrix.org
Will you send logs?
Yes
Can't send logs (gives me an error), I can upload them somewhere else if needed.
We have activated "feature_group_calls" for the Element App.
As of 1.11.58 (still in 1.11.60) we have the same problem, even with normal Element Calls 1:1 or Group Calls it doesn't matter. If you click on another room, you are kicked out of the can and when you get back in, you can no longer hear anyone.
We are using macOS Version 14.
We have activated "feature_group_calls" for the Element App.
As of 1.11.58 (still in 1.11.60) we have the same problem, even with normal Element Calls 1:1 or Group Calls it doesn't matter. If you click on another room, you are kicked out of the can and when you get back in, you can no longer hear anyone.
We are using macOS Version 14.
Similar situation here, we use Element call for our video rooms. But I've not been able to push a new version of Element to my users due to this issue.
Tested it again and it's still present in 1.11.60, (Windows, Element web, Chromium: 122.0.6261.111).
I've got a buddy of mine to send you logs of this behavior with a reference to this issue.
On Element Nightly I found that if I remove the config.json the problem is no longer there. The problem also occurred if the config.json only contains "{}".
This still happens sometimes on Linux/Element Desktop, Windows/Element Desktop and Windows/Firefox/Element Web.
I feel like this issue isn't appearing that often anymore. I just encountered it yesterday though, so it is still existent.
I think this issue doesn't exist anymore.