Commit f07039f
committed
Fix handling of signaling message responses when joining a room
When joining a room, the signaling server confirms that joining the room
was successful by sending a "room" message. Until now the Android app
assumed that "room" messages were sent only in that case, but a "room"
message can be sent also if the properties of the room change. When the
room is joined while the call activity is active the call is also
joined, so if the properties of the room changed while in a call the
Android app rejoined the call, which caused strange issues due to how it
was done. For example, when a recording started additional guests
appeared in the UI.
To solve that now only the "room" message that actually confirms that
the join was successful, which can be identified by setting an ID in the
request to join the room, is treated as such.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>1 parent 947ada1 commit f07039f
File tree
1 file changed
+5
-3
lines changed- app/src/main/java/com/nextcloud/talk/webrtc
1 file changed
+5
-3
lines changedLines changed: 5 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
165 | 165 | | |
166 | 166 | | |
167 | 167 | | |
168 | | - | |
169 | 168 | | |
170 | 169 | | |
171 | 170 | | |
| |||
396 | 395 | | |
397 | 396 | | |
398 | 397 | | |
| 398 | + | |
| 399 | + | |
| 400 | + | |
399 | 401 | | |
400 | 402 | | |
401 | 403 | | |
402 | 404 | | |
403 | | - | |
| 405 | + | |
404 | 406 | | |
405 | 407 | | |
406 | 408 | | |
| |||
413 | 415 | | |
414 | 416 | | |
415 | 417 | | |
416 | | - | |
| 418 | + | |
417 | 419 | | |
418 | 420 | | |
419 | 421 | | |
| |||
0 commit comments