-
Notifications
You must be signed in to change notification settings - Fork 131
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
Built app with Xcode 15.2 crashes after AppSyncClient subscribe on iOS 16.3.1 version or lower #587
Comments
Hi @CJblaze2022, thanks for opening this issue. From what I found online, this crash happens when attempting to use As a quick fix, you can update both Note that this will be overwritten every time you do a
We're already working on bumping the minimum deployments for these pods to iOS 12:
Once these are merged and released, you won't need to manually update anything. |
hi @ruisebas so sorry for the late response, we were testing you solution (it is not easy to find iOS 15 and 16 devices 😅), we changed our |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
We were working with Xcode 14.3.1 and made all the configurations to integrate appSync in our project, everything works as expected.
Recently we updated Xcode to 15.2 and the app crashes and stop working after AppSyncClient subscribe and shows EXC_BAD_ACCESS, we don't have crashes with iOS 16.6 devices or higher, crash occurs with lower iOS versions like 16.3.1, 16.1.1, 15.5, etc.
We used
3.1.2
Appsync version for our setting up, we tried with3.6.4
and issue continues.Currently we went back to Xcode 14.3.1 to deliver builds into TestFlight, now we are facing this apple warning (this is the reason why we switch from Xcode 14.3.1 to 15.2).
To Reproduce
call
subscribe
method for AppSyncClient.Expected behavior
Call
subscribe
method for AppSyncClient without crash for devices with iOS 16.3.1 version or lower.Screenshots
Environment(please complete the following information):
Device Information (please complete the following information):
Additional context
There is a related issue for
amplify-flutter
and it wasn't solved yet aws-amplify/amplify-flutter#4195The text was updated successfully, but these errors were encountered: