Continue to connect even when initial connection fails #3068
+20
−34
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@Nardol can you try out this branch and see if it solves the IPv6 issue. Also use latest libTeamTalk5.so |
Contributor
|
I've just recompiled libraries, made an apk from this branch and unfortunately, even after the message specifying a new attempt connection is never successfull. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change addresses the issue #3045 where getaddrinfo() may return EAI_AGAIN on Android. By continuously calling TeamTalk5.connect() in TeamTalkService it has the same effect as calling getaddrinfo() multiple times.
Hopefully this change resolves #3045.