Restore iOS-like NWPath handling on MacOS app #3
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.
Sometimes after a network path change, especially when only "unsatisfied" network path is available, for example when a laptop is loses all LAN and WiFi networks, further network path changes are ignored. When "satisfied" networks disappear the cloned route for the bound socket is removed by the system and WireGuard packets are routed through the tunnel. This will result in an non-operational tunnel.
The iOS code does not manifest this behaviour, as it properly disables the tunnel when no "satisfied" networks are available. Remove the special MacOS case, use the iOS code on MacOS app.