Seed NetworkMonitor
state from currentPath
to eliminate offline race at startup
#259
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.
Follow-up to #229
@pcuenca observed that tests were failing locally because
shouldUseOfflineMode
was occasionally evaluatingisConnected
to befalse
. This new behavior occurred after switching to Swift Testing, in #229. That PR didn't change anything about offline mode, but it did increase test parallelism, which I suspect surfaced a race condition in the network monitor.This PR updates the network monitor to seed the offline / online state immediately from
NWPathMonitor.currentPath
after callingstartMonitoring
. This should fix intermittent offline-mode activation that's observed running tests locally.