Open eklipse2k8 opened 3 weeks ago
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!
I believe that we're getting a similar crash at launch with Xcode 16 beta.
Hey @fishandphil @eklipse2k8 thanks for your reports!
We're aware of this issue and already filed FB13828346 with Apple.
The issue seems to manifest only when compiling with Xcode 16, and running on iOS 17/macOS 14.
We're trying to find a workaround while Apple gets back to us. We'll keep you posted.
Meanwhile, you can test your apps by running on an iOS 18 simulator or device.
Sorry for the inconvenience!
The same issue also appears on devices running iOS 15.
Filed an issue in the Swift repo:
got the same issue with both iOS 18 beta and iOS 17.4. seems like it doesn't point to the code that crashed on 18.0 beta, only on the iOS 17 emulator
Is there a known version of the SDK that we know isn't having this issue? Seeing this on 17.4 also
Is there a known version of the SDK that we know isn't having this issue? Seeing this on 17.4 also
it's on anything prior to ios 18 beta on Xcode 16 beta. the only version that works is ios 18
Confirming that this is still an issue on Xcode 16 beta 2.
The same
Are there any plans for a workaround, just in case the Swift bug is not fixed swiftly enough?
Edit: it seems like it's fixed already https://github.com/swiftlang/swift/issues/74333#issuecomment-2195013992
Installed release/6.0 (June 22, 2024), and the crashes are still there.
Describe the bug When attempting to initialize the latest SDK, I am getting an EXC_BAD_ACCESS in the call to
ETagManager.Response.encode(to:)
Environment
usesStoreKit2IfAvailable(true)
)Debug logs that reproduce the issue. Complete logs with
Purchases.logLevel = .verbose
will help us debug this issue.This is happening during app launch, so not much I can do.