Given this bug, it's likely that folks have downloaded the app, not been presented with the ATTTrackingManager prompt and the response has defaulted to "Denied". Does anyone know if it's possible (or planned) to allow that prompt to be re-triggered after the fix?

Apple? Bueller? Bueller? Apple? Is anyone going to chime in on this problem?!? Why is every upgrade to XCode so painful?!? Personally, I don't really care if DOJ thnks Apple has a "monopoly". Apple's existence helped me to create my own small business. BUT, frankly, I'm really fed up with having to spend 3,4,8, 12 hours getting my projects to build properly every time they update their Mac O/S and XCode. With a trillion $ market cap, I think it's reasonable to expect that that they, as a "partner" would test their releases better! The amount of time and money I spend getting things "back to square 1" after an Apple update is ridiculous!

I can upload builds if you need them, but it would appear to be pretty obvious that there is a big problem with XCode16. This same project was successfully built and deployed with XCode 15 before I upgrade my Mac and XCode last night

Has anyone figured out how to get the attachments button to be enabled? I'm assuming something changed in IOS 18 because my users have been using this view for years to send text messages with screenshot attachments.

same issue. Debugger is not stopping in "source code"; it's stopping on a decompiled thread source

Definitely an issue in xCode 16.3 as it applies to inherited properties and the simulators. I can't diagnose "why" it's happening, but there are cases where the value shown in the debugger is not what it should be and that causes code to fail. What's crazy is that looking in the debugger at self.inheritedProperty and then expanding self and drilling down to "inheritedProperty", the values do not match. The value on the "self" node is correct. The issue does not occur on a real device and Xcode 16.0 is still solid as it applies to simulators. Personally, I will be avoiding xCode 16.3 until Apple issues an update that addresses a fix for this.

ditto ... +1

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.