Storekit configuration broken in Xcode 16.4 the file has been changed

Question

Colokol OP

Created 1w

Replies 3

Boosts 1

Participants 3

Hi everyone,

After updating to Xcode 16.4, my StoreKit configuration stopped working. Whenever I run the app with a .storekit file set as the active scheme, I immediately get this alert:

“The file has been changed. Do you want to save your changes or revert to the file on disk?”

No matter if I choose Save Anyway or Revert, StoreKit testing does not work - the purchases are not simulated, and the scheme is basically broken.

This issue didn’t exist in Xcode 15.4 - the same StoreKit configuration file works fine there.

What I tried so far:

Clearing Derived Data - no effect

Making sure no scripts/tools modify the .storekit file - still happens

Restarting Xcode and macOS - no change

Environment:

Xcode 16.4

Happens in both Simulator and on device

Reproducible 100%

Has anyone else seen this in 16.4? Any known workarounds until Apple fixes it?

Thanks!

Boost

Answer 1

DTS Engineer OP

Apple

1w

Are you able to reproduce this issue when you recreate the file?

0

Answer 2

DannyByersII OP

1w

I am experiencing a similar issue using an Xcode 16.4 with a simulator running IOS 18.6

I receive a series of this message when trying to load products from the StoreKit configuration file:

Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue)

If I enable Zombie Objects in the debugger, I also get these messages:

Class _NSZombie_SKProductInternal is implemented in both ?? (0x1347517a0) and ?? (0x1347517d0). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed.

I've tested the file on a handful of older simulators and everything works fine; neither error is reported on an IOS 18.0 simulator.

I've also verified that things are working as expected with TestFlight so I'm less concerned about going to Production.

Still, it would be nice be have a much higher level of confidence that there is not a serious bug somewhere before I roll out my next Production release.

1

Answer 3

Colokol OP

1w

Are you able to reproduce this issue when you recreate the file?

0 comments

0