-
Notifications
You must be signed in to change notification settings - Fork 198
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
EXC_BAD_ACCESS on Xcode 16 Beta 5 with iOS 18.1 Beta #3806
Comments
Attaching minimal reproducible example of the crash. Please note that you need to add your own |
I've noticed this issue also happening in Line 204 of /smithy-swift/Sources/ClientRuntime/Networking/Http/URLSession/URLSessionHTTPClient.swift
Since this issue does not happen on Xcode 16 beta 4 (16A5211f), it's starting to look like an Xcode regression to me so I have filed a radar with Apple as well (FB14768097) |
Thank you for posting the stack trace and a sample project - can you please paste verbose logs with sensitive information removed, when you encounter the crash mentioned? You can enable verbose logs like below
Our team will try to reproduce this issue and post updates here. |
This issue seems to have come from Xcode/iOS side and is resolved on the latest Xcode 16 RC and iOS 18 RC. Closing for now. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
I'm using AWS Amplify and Ampify UI liveness in my Swift project. The app functions well on Xcode 16 beta 1 however when built with Xcode 16 Beta 5, the app crashes on startup with EXC_BAD_ACCESS. Please see log
Steps To Reproduce
Expected behavior
App does not crash and initializes Amplify correctly.
Amplify Framework Version
2.35.4
Amplify Categories
Auth, Storage
Dependency manager
Swift PM
Swift version
5
CLI version
12.12.1
Xcode version
16.0 beta 5 (16A5221g)
Relevant log output
Is this a regression?
Yes
Regression additional context
Xcode 16 Beta 1 works fine
Platforms
iOS
OS Version
iOS 18.1 (22B5007p)
Device
iPhone 15 Pro
Specific to simulators
No, runs fine on simulator
Additional context
No response
The text was updated successfully, but these errors were encountered: