mirror of
https://github.com/nextcloud/spreed.git
synced 2025-12-18 05:20:50 +01:00
fix: Fix leaving call if a signaling message is received while reconnecting
When the local participant is in the call and a signaling message does not list the participant as being in the call the call is left (as it is assumed that, for example, the participant was kicked out from the call by a moderator). During a forced reconnection the local participant was not marked as "not in the call" when the call was left, so in the time between sending the request to join the call again and receiving a signaling message confirming that the call was joined another signaling message that does not list the participant yet as in the call caused the UI to leave the call (for example, if another participant also joined). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This commit is contained in:
parent
9d7faf9345
commit
527f24a2bb
1 changed files with 5 additions and 0 deletions
|
|
@ -619,6 +619,11 @@ export default function initWebRtc(signaling, _callParticipantCollection, _local
|
|||
// cases the call should be kept active from the point of view of
|
||||
// WebRTC.
|
||||
if (reconnect) {
|
||||
// The signaling state must be marked as not in the call to prevent
|
||||
// that after joining the call again the local participant is
|
||||
// treated as in the call before a signaling message confirms it.
|
||||
selfInCall = PARTICIPANT.CALL_FLAG.DISCONNECTED
|
||||
|
||||
return
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue