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.

ditto ... +1

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.

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

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.

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

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!

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?

Anyone at Apple have an idea on this?

Thanks, Quinn! So long as I will know there is a problem when I attempt to build in XCode, that should be good enough.

I'm not sure that I count as an In-House (Enterprise) team. At the end of the day, "I'm just a guy, standing in front of an App Store, praying that this cert won't expire and create issues when I try to push another release of my app" ;)

Not sure how I missed this reply. Thank you, Eskimo. But, I still don't know if I'm supposed to do anything about the cert that did not rotate in January as it was schedule to do. It expires in 5 days. Am I supposed to use the link to manually rotate it?

I always get nervous about "renewing certs" because it's a once in a year affair and I don't fully understand the process. I just "follow my notes" and hope I don't mess something up. This year is a little bit different because I started to use "Managed Signing" in XCode by checking the "Automatically manage signing" box in XCode. Normally, I have a "Development" cert and a "iOS Distribution" cert. They were to expire at the end of April. So, after getting a successful update posted to the App Store, I started the update process. I was able to get the two certs I'm used to replaced (and revoked the older certs) and was able to get XCode and my keychain updated. Everything appears to be working fine. "Good to go" for another year! However, there is a "Distribution Managed" cert on my account that is set to expire 2024/04/28. The cert is also designated with an "Automatic Certificate Rotation Date" of 2024/01/29. I have two questions: Am I supposed to do something with this cert since it apparently didn't get "automatically rotated" on 1/29/2024? Should I be concerned about being able to push updates when this cert expires? Given that signing is being automatically managed, do I still need to maintain the 'iOS Distribution" cert? Is it redundant to the cert being used by managed signing? Thanks in advance.

I created the file "PrivacyInfo.xcprivacy" and included it in my project with the keys that I was notified were required. However, I get the same email complaining that these four entries are missing: NSPrivacyAccessedAPICategoryDiskSpace NSPrivacyAccessedAPICategoryFileTimestamp NSPrivacyAccessedAPICategoryUserDefaults NSPrivacyAccessedAPICategorySystemBootTime Is there something else that's required for the newly added privacy manifest to be recognized during review? The file is currently located at the root directory of my project; next to the .xcodeproj file I'm using XCode 15.2.0

Same issue here, but it's no longer sporadic. It's almost every time that I open XCode or a simulator that hasn't been opened before. Is anyone looking into this issue? Failing to select "Keep Xcode version" results in the app crashing.