You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simulate a bad connection on one device by enabling the 100% Loss profile in Network Link Conditioner.
Expected behavior
The connectionState changes to .reconnecting on the first reconnect attempt.
Observed behavior
The connectionState stays as .connected while the retry attempts are exhausted. The connectionState then changes to .reconnecting, and then to .disconnected.
Logs
Relevant logs:
[Retry] Attempt 1 of 3, delay: 2.0
[Retry] Waiting for 2.0 seconds...
[Retry] Attempt 2 of 3, delay: 2.0
[Retry] Waiting for 2.0 seconds...
Did update connectionState .connected -> .reconnecting
Did update connectionState .reconnecting -> .disconnected
Ok. Is there any other way to currently observe the connection state of the user when reconnecting? The experience we able to build for the disconnected user now is that it seems everyone else has disconnected from the call.
Describe the bug
When attempting to reconnect the
connectionState
remains as.connected
until all retry attempts have been exhausted.SDK Version
2.0.10
iOS Version
17.5.1
Steps to Reproduce
Expected behavior
The
connectionState
changes to.reconnecting
on the first reconnect attempt.Observed behavior
The
connectionState
stays as.connected
while the retry attempts are exhausted. TheconnectionState
then changes to.reconnecting
, and then to.disconnected
.Logs
Relevant logs:
Full logs if that would be of any help:
The text was updated successfully, but these errors were encountered: