@Smithers awesome, glad to hear you're finding the same thing. Yeah I sure wish Crashlytics gave build numbers, would have saved a lot of effort on this one.

@DTS Engineer thanks for the replies! Reupping my feedback (FB15135298) over in this thread. Crash reports are about all I've got for you but happy to attach more to that feedback if it will help. Now we're a little ways into the iOS 18 rollout, and I'm not seeing an explosion of crashes from this issue. (I do continue to see a few users encountering it though). And, I still haven't seen any crashes for which I can get an iOS build number that were running beta 5 or later. So my thinking is that this must have gotten fixed in the later iOS 18 betas, there's some pool of folks still on earlier betas out there, and they are the source of these reports. Would love confirmation if that's the case!

FB15135298 We shipped an app update built with Xcode 16 RC and are now seeing similar crashes in the wild. They're all EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000004, and in each the first line in the stack trace is a call to withCheckedContinuation or withCheckedThrowingContinuation. Everybody else encountering the issue seems to think it was fixed in Xcode 16 beta 6, so I'm surprised to see this. However, for the crashes where we have info on the specific build of iOS 18 are running beta 4 or earlier. Did this get fixed, but the fix also needed one of the later iOS 18 betas as well as a newer Xcode?

Just writing in to add I'm still seeing this on with Xcode 15.3 (15E204a) and iOS 17.5. Thomas Rued above seems to be correct -- this looks like a permissions/ownership issue in when the container is replaced, and making everything world writable 'fixes' the issue. (But then of course, permissions in the replaced container are then different than if the container hadn't been replaced).