Yes, SwiftData is great, but until it is only marginally useful if we can't easily sync data across devices or share data with other users.

I am having the exact same issue, and modelContext.save() resolves it. I will be eager to hear more on that Feedback Report.

Hello Jordan, I think this will work. I will let you know. The Medium article refers to the Hacking With Swift article and seems to solve the problems mentioned in it. I'll get back to you on this after I've finished trying to implement it.

I had various issues trying to implement the suggested approach, largely because my architecture is quite different than what is in the article. Xcode AI helped but eventually led me to just make scratch copies of the data to be edited.

Hello, I am planning a project using SwiftData and inheritance with CloudKit but I am quite concerned about running into this bug. When I click the link to the FB ID above, it comes up empty as do searches for it. Does anyone know the current status?

Hi, I am in a similar situation and called a support number. They said they are very behind on these and that there is no specific timeline for completion.

I encountered another bug with SwiftData and inheritance and reported it (FB21837287). This one is not related to CloudKit. Briefly, SwiftData crashes during auto-save when the schema contains: A base @Model class with at least one subclass (inheritance) A separate @Model class with a reference to the base class The crash occurs specifically when: There is a class inheritance hierarchy (Beta: Alpha) A separate class (Standalone) has a reference typed as the base class (Alpha?) Changing the reference from var ref: Alpha? to var ref: Beta? (subclass) eliminates the crash.