-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[Bug]:(IOS crash) NWPathMonitor Thread 1: EXC_BAD_ACCESS (code=1, address=0x0) #1955
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
Comments
I also got the same error |
same error |
Same error but build runs perfectly on ios 17 beta 3 |
Its strange that no one has posted solution to this problem! Its occuring in iOS 16.5.1 as well Xcode 15 Beta. App works fine in old iOS and also in iOS 17 on simulator but doesn't work in iOS 16.5.1. Just upgraded iOS to 16.6 now and still no luck. Same error! |
I'm getting this same bug on iOS when I include the amplify_api package since it pulls in the connectivity_plus package. |
Same error |
Ok, just got to the temporary solution for this, i'll post the things i did to avoid this error. Changed build Targets in pod and runner to 12.0 |
Thanks @madilsharief, you figured it out. The issue is XCode 15 beta 4. It works fine with XCode 14.3.1. That's all I changed and it worked right away:
But heading out for vacation so I don't have time to get a minimal POC over to the XCode team to fix this! |
Are there any updates on this? I'm still able to reproduce in Xcode 15 beta 7 (released August 22nd) when running on iOS devices that are on OS version 16.6. Confirmed the issue is due to the connectivity_plus dependency and still reproduces on the latest version of connectivity_plus (4.0.2) |
Haven't tested on flutter myself, but this looks like a problem related to XCode 15 removing support for iOS < 12.
|
I got the same error anyone find the solution? |
Thank you, this works for me. |
@sareth5555 note that manually changing the deployment target of a Pod will be reset on each |
I would ask someone among people with this problem to validate the fix for the plugin. To do so, add the plugin the following way:
UPD (Oct 3 2023): Because the PR with the fix is already merged updated the snippet to point to exact commit with the fix on |
Thank you, it's worked for me. |
This is not changing the deployment target in any Pod. You just change it
in the main project. So there is no any effect if you do pod install.
…On Fri, 22 Sep 2023 at 3:40 PM Enrico Zannini ***@***.***> wrote:
@sareth5555 <https://github.com/sareth5555> note that manually changing
the deployment target of a Pod will be reset on each pod install.
—
Reply to this email directly, view it on GitHub
<#1955 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIA5X2XVTPQH3VN22JPQCP3X3VFH3ANCNFSM6AAAAAA2DV7KEY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@vankhanh0911 @sareth5555 I would encourage you to try the update for |
Info for those arriving to this issue when Googling and still having this issue: The issue is confirmed when building for iOS <17, active issue is here #2276 |
I have the some problem after updating Mac and iPhone OS. |
It worked for me too. Thanks! |
I just updated connectivity_plus to 5.0.1, and it worked (I already had the min deployment target above 12, but that didn't work) |
The issue has been solved. I hope it can help you guys and prevent similar problems in the future.✅ Link solution : https://stackoverflow.com/a/77643660/22005920 |
Platform
Ios +15
Plugin
connectivity_plus
Version
4.0.0
Flutter SDK
3.10.5
Steps to reproduce
Hi ,
when run the app on real device on release run I got iOS crash as screenshot shows :
Code Sample
No response
Logs
Flutter Doctor
Checklist before submitting a bug
flutter pub upgrade
flutter clean
The text was updated successfully, but these errors were encountered: