ARTICLE AD BOX
I’m working on an iOS app using Core Data with CloudKit synchronization (NSPersistentCloudKitContainer).
In my Core Data model, I have defined relationships between entities (e.g. 1:n and n:m). These relationships and constraints are clearly set up in the .xcdatamodeld file.
However, after enabling CloudKit and letting the schema initialize in the iCloud container, I noticed that these constraints (relationships, cardinality, etc.) do not seem to be reflected in the CloudKit schema as I would expect.
From what I can see:
• The record types are created in CloudKit
• Fields are present
• But relationships and constraints are not represented in the same way as in Core Data
This leads me to a few questions:
Is it expected that Core Data relationship constraints are not explicitly mirrored in the CloudKit schema? How does CloudKit internally handle relationships defined in Core Data? Are developers expected to enforce these constraints manually at the app level? What is the recommended best practice for ensuring data integrity when using Core Data + CloudKit?In Apps before, I had add in every entity a self created uuid and add this manually in every related datarow. so I had also created a n:m Tabele. But this is in my mind fully agains the ability of core data.
Please can you tell me if i would only need a option that icloudkit would work with the native relationship or the real possible way be only the selfcreated keys.
