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
#167
says that, after a disconnect caused by a network outage, then waiting
long enough for the connection to go disconnected state and the channels
to be detached, an explicit AblyRealtime.connection.connect() is not
immediately actioned. Instead it does not connect until up to a couple
of minutes later.
It looks like the condition is incorrect in ConnectionManager.connect()
to see if a connection attempt is already underway, so the explicit
connect does not do anything. Instead it waits until the next time it
would have attempted a reconnect anyway.
Fixed.
Also fixed so that the connect happens even if there is a connection
thread already started.
This from a customer:
I enter aeroplane mode. The connection is lost, eventually, the connection type changes to suspended and the channels detach. All good.
The logs read:
At this point, I show a "retry" button on the screen.
In my testing, I now come out of aeroplane mode and wait a few seconds to ensure there is a good connection to WiFi/4G.
I tap the retry button which calls the following code:
You can see the time of this in the log under "WILL TRY TO RECONNECT NOW"
At this point, absolutely no ably logs are generated, so the ably client is doing nothing at all, even though I called connect.
Nearly 2 full minutes later, it attempts to connect, and does so:
The text was updated successfully, but these errors were encountered: