Fixed Data race condition in Network Reachability #51
Conversation
This file contains 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
|
Looks good |
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.
establishConnection() in RetryMechanism.swift internally checks for networkAvailability with Reachability which updates network status flags and triggers notifications in async.
observerNetworkConnectivity() adds observers for reachable and not-reachable state.
This sequence of events leads to race-condition for whenReachable and whenUnreachable observers as those are being set and get at the same time from different threads.
This MR changes sequence of events. With these changes, we add the observers first and then check for network status and try to establishConnection.