Skip to content
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

Realtime suspended connection retrial using wrong timeout #913

Closed
ricardopereira opened this issue Oct 27, 2019 · 0 comments
Closed

Realtime suspended connection retrial using wrong timeout #913

ricardopereira opened this issue Oct 27, 2019 · 0 comments
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@ricardopereira
Copy link
Contributor

Which version of the Ably SDK are you using?

v1.1.11 - Beta 1

On which platform does the issue happen?

iOS 13

Which version of Xcode are you using?

Xcode 11.1

What did you do?

I set my iPhone to flight mode and the connection moved to DISCONNECTED as expected but the connection retrial seems to not respect RTN14e.

(RTN14e) Once the connection state has been in the DISCONNECTED state for more than the default connectionStateTtl, the state will change to SUSPENDED and be emitted with the reason, and the Connection#errorReason will be updated. In this state, a new connection attempt will be made periodically as specified within suspendedRetryTimeout of ClientOptions.

The network connection is down: moves to DISCONNECTED and retries after 15s again and again until the connectionStateTtl is reached and then it moves to SUSPENDED. The connection retries after 30s (SUSPENDED -> CONNECTING) but fails and moves to DISCONNECTED. Then the library starts again with retrials of 15s (DISCONNECTED to CONNECTING).

What did you expect to happen?

Moving from DISCONNECTED (15s) -> CONNECTING (fails) -> DISCONNECTED (15s) -> CONNECTING (fails) -> DISCONNECTED ... after TTL --> SUSPENDED (30s) -> CONNECTING (fails) -> SUSPENDED (30s) -> CONNECTING (fails) -> SUSPENDED (30s) ...

What happened instead?

Moving from DISCONNECTED (15s) -> CONNECTING (fails) -> DISCONNECTED (15s) -> CONNECTING (fails) -> DISCONNECTED ... after TTL --> SUSPENDED (30s) -> CONNECTING (fails) -> DISCONNECTED (15s) -> CONNECTING (fails) -> DISCONNECTED (15s) -> CONNECTING (fails) -> DISCONNECTED ... after TTL --> SUSPENDED (30s).

@ricardopereira ricardopereira added bug Something isn't working. It's clear that this does need to be fixed. realtime labels Oct 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. It's clear that this does need to be fixed.
Development

No branches or pull requests

1 participant