-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[connectivity_plus] Add NWPathMonitor based ConnectivityProvider for iOS #791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[connectivity_plus] Add NWPathMonitor based ConnectivityProvider for iOS #791
Conversation
|
Both iOS and MacOS plugins with I would suggest to keep backing implementation ( |
|
Thanks for the PR @kuhnroyal in the coming days I will take a look at the code and give it a try |
|
Sorry @kuhnroyal I couldn't go through your PR yet. Any chance you can fix the merge conflicts? |
* copied from MacOS implementation * available on iOS 12+ * correctly notifies when switching between Wifi networks without internet access
* noticeable mainly after hot restart
* ensure early initialization of backing `Reachability`/`NWPathMonitor` resulting in `checkConnectivity()` returning the correct status right away (until now it almost always returned `.none`) * having the correct initial status results in the the status stream not emitting double events on startup (previously most of the time it emitted 2 events starting with `.none` following the correct status) * the behavior is still incorrect after a hot restart because the backing `Reachability`/`NWPathMonitor` has been cleaned up and is not initialized early
ce87bec to
c8235da
Compare
|
@miquelbeltran Rebased |
|
Yea that is what I hope. |
@miquelbeltran Do you have thoughts on this? |
|
your explanation makes sense, yes. I haven't looked into it tho. |
Description
Related Issues
Fixes #632 for iOS 12+
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process.
pubspec.yamlandCHANGELOG.md.///).flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?