I have recently been experiencing issues in the Production Environment as well, although I cannot confirm if it is the same situation. My app is Mac only. I am adding iCloud support to an existing app that is already on the Mac App Store. I am testing such support via TestFlight builds. I am not using SwiftData but traditional Core Data with NSPersistentCloudKitContainer. – When making use of the Production Environment, only partial synchronization took place. This has not been an issue when run in the Development Environment. This occurred multiple times even when testing using accounts with different App IDs. My only thought was that perhaps iCloud also needed to be enabled as a Capability in Certificates, Identifiers & Profiles. That did not end up being the case. However, I was surprised to see that two iCloud Containers were enabled for this app even though only one was selected for the target in Xcode. After removing the unused container from the list and saving, I performed the following actions on two Macs. I deleted both the local and cloud data (Settings > iCloud > Manager…). I then restarted and gave it another try. Full synchronization occurred, just as it had when using the Development Environment. From your screenshot, it appears that you have created more than one iCloud Container. However, best I can tell, it cannot be determined from Xcode if both of them will be enabled in Certificates, Identifiers & Profiles. I need to do a bit more testing before I can confirm that removing the extra container truly was the fix.

Apologies for my poor choice of words. I was referring to tests using the sandbox environment. Because test users are not real users and no money is exchanged, I typically think of such tests as simulations.My reason for posting is that I have been unable to replicate the crashes, as I have had no issues when testing my app using the sandbox environment. I am trying to get to the bottom of the situation and was wondering if anyone else had experienced such a situation in the past.

The system would be calling exit if the app is crashing on the initial launch. Although I do call exit 173 within the app if verification fails, no verification is performed on the initial launch. When running a test under the sandbox environment, I set breakpoints on both exit(173) and the creation of the verification class to ensure that neither is executed during the initial launch. Neither breakpoint was triggered.> When App Review tests an IAP they do it in the sandbox. The procedure is to first send to this website and if you get a 21007 error to test against the sandbox.My code does implement verification in this fashion. I can confirm that verification does succeed when making a purchase on my own Mac using the sandbox environment with a test user.