`Xcode 16` / `iOS 18`: Thread 21: EXC_BAD_ACCESS (code=1, address=0xfffffffffffffff8) in ETagManager.Response.encode(to:) about purchases-ios HOT 21 CLOSED

Hello! The fix for this issue in the Swift runtime has finally shipped with Xcode 16 beta 3. Please download and try.

We're sorry for the trouble this has caused. We reported this issue to Apple immediately after the first Xcode 16 beta came out, but development cycle timing meant the fix only came out in beta 3.

Thank you everybody for your patience and for reporting bugs.

Mark.

from purchases-ios.

Confirming that this is still an issue on Xcode 16 beta 2.

from purchases-ios.

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 swiftlang/swift#74333 (comment)

from purchases-ios.

Installed release/6.0 (June 22, 2024), and the crashes are still there.

from purchases-ios.

It is now fixed on Xcode beta 3.

from purchases-ios.

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

from purchases-ios.

I believe that we're getting a similar crash at launch with Xcode 16 beta.

from purchases-ios.

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!

from purchases-ios.

The same issue also appears on devices running iOS 15.

from purchases-ios.

Filed an issue in the Swift repo:

swiftlang/swift#74333

from purchases-ios.

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

from purchases-ios.

Is there a known version of the SDK that we know isn't having this issue? Seeing this on 17.4 also

from purchases-ios.

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

from purchases-ios.

The same

from purchases-ios.

Facing similar issue but on different line. (Same file).

Just a question, will my app work on TestFlight if I push it using Xcode 16 beta 2?

from purchases-ios.

Facing similar issue but on different line. (Same file).

Just a question, will my app work on TestFlight if I push it using Xcode 16 beta 2?

It will only work on iOS 18 beta devices on TestFlight. Keep in mind you cannot publish to the App Store with beta versions of Xcode. You can publish to TestFlight but, again, this issue will prevent any devices not on the beta from working properly.

from purchases-ios.

Facing similar issue but on different line. (Same file).
Just a question, will my app work on TestFlight if I push it using Xcode 16 beta 2?

It will only work on iOS 18 beta devices on TestFlight. Keep in mind you cannot publish to the App Store with beta versions of Xcode. You can publish to TestFlight but, again, this issue will prevent any devices not on the beta from working properly.

Ah! Had an urgent delivery today. Seems like I need a new MacBook

from purchases-ios.

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 swiftlang/swift#74333 (comment)

How? Any light on this?

from purchases-ios.

Can someone from RC please give us an update?

from purchases-ios.

Having same issue here and no issue running on iOS 18 simulators with Xcode 16.

from purchases-ios.

I finally resolved it, not actually a solution but can be a lifesaver for someone who is in urgency. I tried everything I could (Including installing Xcode 15.4 and able to run it through command line). It will fail to push to the AppStore as it can't access your keychain for some reason and can't access the certificates. Spent hours resolving it.

My final resort was go to the recovery (ctrl + cmd + R on boot). Erasing the HDD, Install the previous macOS, install Xcode again and pushing the release. Amazing and disappointing how such small things can break your source code and the creators have absolutely no idea.

from purchases-ios.