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

Avoiding premature reconnect due to exceeded threshold #1883

Merged
merged 1 commit into from
Mar 8, 2024

Conversation

maratal
Copy link
Collaborator

@maratal maratal commented Mar 1, 2024

To avoid premature reconnect due to exceeded threshold while CONNECTING, reachability now activated after token request is completed. During token request user will receive the request error in case of unreachable network.

Closes #1882

…NG, reachability now activated after token request is complited. During token request user will receive the request error in case of unreachable network.
@maratal maratal changed the title Avoiding premature reconnect due to exeeded threshhold Avoiding premature reconnect due to exceeded threshhold Mar 1, 2024
@maratal maratal changed the title Avoiding premature reconnect due to exceeded threshhold Avoiding premature reconnect due to exceeded threshold Mar 1, 2024
@maratal maratal merged commit 15d79cb into main Mar 8, 2024
7 checks passed
@maratal maratal deleted the fix/1882-fix-reachability-activation branch March 8, 2024 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

singleton realtime instance obtains multiple connections and confuses them
2 participants