-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnknownDeviceDialog box breaks VoIP in E2E rooms #3285
Comments
See also #2669 |
see also #3124 |
it's also a problem for the person receiving the call (where the call then rings forever etc) |
Are we sure this is fixed? It feels to me that the UDD is showing up a long time you try to hit 'Answer', and then appears multiple times, even if you say "Send anyway"? |
@ara4n I wonder if more than one event is being sent at once, triggering 3 UDEs and 3 consecutive UDDs... Yep I've confirmed this. I'm too sure how the signalling works so I'm not sure why this would happen, but I've confirmed that 3 UDEs occur when starting a call. So I think we need to de-dupe dispatches for the UDD, only ever showing one. This is OK because send anyway sends all unsent events. It might be a good idea to show which events are unsent in the dialog somehow. |
When starting a call, several events are sent and if some devices are unverified, all three will trigger their own UnknownDeviceError. This causes three overlapping, identical UnknownDeviceDialogs. This change effectively dedupes the dialogs so that only one is shown. This is safe to do because the UDD allows resending of _all_ events that were left unsent. Fixes element-hq/element-web#3285
The VoIP call silently fails rather than coughing up the dialog box.
The text was updated successfully, but these errors were encountered: