[AND-205] Improve network connectivity check in the NetworkStateProvider. #5538
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.
🎯 Goal
Linear: https://linear.app/stream/issue/AND-205/race-condition-in-networkstateprovider-causes-the-connectionstate-to
Fixes a rare bug where turning off the network connectivity on the device doesn't update the
ConnectionState
toOffline
.The cause for this is that it is not safe to call
ConnectivityManager.getNetworkCapabilities(Network)
from theConnectivityManager.NetworkCallback.onLost
callback, as there is no guarantee that theConnectivityManager
state will be in the updated state from the callback. In some occasions, callingNetworkStateProvider.isConnected()
from theNetworkCallback.onLost
callback returnstrue
, which is a false positive. See details: https://developer.android.com/reference/android/net/ConnectivityManager.NetworkCallback#onLost(android.net.Network)🛠 Implementation details
🎨 UI Changes
NA
🧪 Testing
This was difficult to reproduce with a real device, but it happened quite consistently on an Emulator. To easily reproduce the issue (and then test the fix), you can:
ConnectionState
ConnectionState
will NOT change toOffline
when turning off the connectivity, even though the device is not connected to the internet. If you are testing with the fixed version, this should no longer happen.Provide the patch summary here