I have the same problem -- I have an app version that is iOS17 only and there is no device / simulator with a 5.5 inch screen that runs iOS17 anymore. That makes generating screenshots for the app store more difficult as there isn't a device with these dimensions that can actually run that app.

More testing shows that if I switch to a different simulator with iOS 17 the structured logging does work as expected for the same project. Does this feature also require iOS 17? Or does it need a different configuration to work with iOS 16? Everything I've seen written about it only mentions Xcode 15 and nothing about a specific iOS version.

Thank you for the reply! I looked in my scheme and there are no environment variables set or extra arguments passed on launch. I even created a new default scheme to test and still have the same results. I do think there is some environment or other value set somewhere that is causing this but it isn't obvious to me where it might be. I tried removing all derived data as well but no luck.

@CrunchyBagel Thank you! That is also helpful. I wasn't aware that initializeCloudKitSchema() was different than just manually promoting from development to production after creating test records within the App but I see what you mean now. I thought that NSPersistentCloudKitContainer created all necessary records in the development environment based on whatever is defined inxcdatamodeld as part of how it works and you then later promote those to production. I see it only creates records based on the specific data that has been uploaded which isn't going to include optional _ckAsset records and other things unless those were specifically needed for the test data. Again, much appreciated!

Amazing, thank you! I did just that and it did offer to push CD_data_ckAsset from development to production afterwards. I knew that it automatically created ckAsset for larger files, but had not occurred to me at all that this never came up in the development environment and so wasn't pushed to production. The error seems more obvious now! The offending image was 756534 bytes but Core Data must have decided to use an external file anyway. Thanks again I really appreciate it!