But given that they have solved this for CloudKit with CoreData and SwiftData, under the hood, is most likely calling through to those APIs, surely an additional attribute of "databaseScope: CKDatabase.Scope = .private" on the ModelConfiguration would solve the issue? Then we can use different ModelContainers for the different scopes. That allows us as developers to choose which container to use for which scope. I'm going to log this via Feedback as an enhancement before too many betas come out
pbcaus
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for