I'm using Core Data and CloudKit together, and so far everything looks great. But one thing that I haven't been able to find much literature on is the interaction between NSPersistentCloudKitContainer and Persistent History Tracking.
My assumption is that NSPersistentCloudKitContainer leans on Persistent History Tracking to execute its responsibilities.
So if we're using Persistent History Tracking elsewhere – maybe to update an app extension using a process similar to the one outlined at https://www.avanderlee.com/swift/persistent-history-tracking-core-data/ – there's a risk of interrupting that process.
Especially with regards to executing a NSPersistentHistoryChangeRequest.deleteHistory(before:) request.
Would this run the risk of deleting history that NSPersistentCloudKitContainer requires to perform its roles?
Is there a way to synchronise these various responsibilities?