-
-
Notifications
You must be signed in to change notification settings - Fork 996
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
fix(connectivity_plus)!: Bump min iOS to 12 to support XCode 15 #2169
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh boi, quite a few issues you've found 🙏🏽
I will wait for a confirmation from one of the users with this problem as I currently don't have a physical iOS device to check the fix. |
Ok, we have a first confirmation: #2155 (comment) Thus, merging to release plugins somewhere this week. |
@vbuberen Directly using this ref is not working either, it's failing at this part still |
Not really familiar with Xcode so not sure where to find the relevant logs to attach, please let me know if I need to send anything specific |
Flutter version: 3.13.6
|
Are you sure you use the patched version? I had confirmation from other people as well that patch worked |
@vbuberen yes, you can see the commit ref in this part of the error, in the path:
|
@vbuberen I was about to update to iPadOS 17 before I ran into this, however considering this issue is happening only on physical devices, should I stay on 16.3 to verify any fixes or provide any logs that might be needed? |
Thank you for such suggestion. What I would ask you to do is to open a new issue where we can continue the discussion. Also, would be great if you provide me with some details of iOS part of your project, like iOS deployment target in that issue. As to updating to iOS 17 or not - if it is Ok for you, please don't update, so we could validate that the fix work if it turns out the problem only happens on iOS 16 (which I doubt and believe that the problem is in the Xcode 15 itself). |
I am able to build the project just fine on my iPhone which is on iOS 17 using Xcode 15. It's happening just on iPadOS 16.3 for me right now. I won't update my iPad for now in case it actually is a <iOS 17 problem.
Will open a new issue with the details in a few mins, would be including the process I used to build for both min 11.0 target and 12.0, anything else you need me to include? |
@vbuberen I was able to get it to work, it wasn't an issue with the plugin, for some reason Xcode was resetting the pod's minimum target to 11, even if the plugin now specifies 12, and it did it for the example project as well (I changed the ref to this fix). Once I saw that, manually setting it back to 12 in the Xcode UI itself, fixed the issue. (I checked the bundled plist of the plugin, it was still saying 12 even before I changed it, but it was 11 in Xcode.) I am not sure why it Is was doing that but the plugin is working fine, it was an issue with XCode, reinstalling it fixed the problem. |
This turned out to be the case after all |
Thank you for researching and providing feedback. It was really helpful. |
this is needed as otherwise there are weird crashes, eg. when opening connectivity view (there are sth. simple as `let monitor = NWPathMonitor()`) as reported eg. at fluttercommunity/plus_plugins#2169 it seems xcode15 does not support ios<12 fully fortunately, this does not change our minimum supported devices as all of them get get ios12.
this is needed as otherwise there are weird crashes, eg. when opening connectivity view (there are sth. simple as `let monitor = NWPathMonitor()`) as reported eg. at fluttercommunity/plus_plugins#2169 it seems xcode15 does not support ios<12 fully fortunately, this does not change our minimum supported devices as all of them get get ios12.
Thanks , you saved my day 👏 |
Info for those arriving to this PR when Googling: The issue is confirmed when building for iOS <17, active issue is here #2276 |
This fixes a crash on iOS devices with any iOS less than 17. See: fluttercommunity/plus_plugins#2169
I get a
error now. Xcode still supports iOS 12.0 though. Is the |
No, it is not required. We already had that issue with Reachability pod some time ago. It is not the plugin, but something else with Cocoapods. |
You have Reachability pod updated locally due to some other dependency, I guess. |
Description
We have multiple bug reports about issues when
connectivity_plus
plugin is used in a project build with Xcode 15. Apparently, after some investigation found out that Xcode 15 supports only iOS 12 and newer and not all APIs work fine.Here is an example of similar solution: https://stackoverflow.com/a/77151438/7339798
In order to support Xcode 15 I am bumping min iOS version for the plugin to 12, so users won't have to modify their build configs on iOS.
Marking as a breaking change to be sure I don't break projects for somebody who still supports <12 iOS versions.
Related Issues
Supposed to close quite a lot of issues:
Fixes #1955
Fixes #2136
Fixes #2154
Fixes #2155
Fixes #2159
Fixes #2162
Fixes #2166
Fixes #2152
Checklist
CHANGELOG.md
nor the plugin version inpubspec.yaml
files.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?
!
in the title as explained in Conventional Commits).