I am writing a SwiftUI App using CoreData + CloudKit, based partly on sample code from `CoreDataCloudKitDemo`.There is a MasterListView which presents a List of NavigationLinks of the available data, eg. Recents, Tags, etc. embedded in a Double Column Style NavigationView.There are 6 @FetchRequest vars that collect the content for the different Sections in the List.They look similar to this:@FetchRequest(fetchRequest: ThingViewModel.fetchRequest(matching: .recent)) var recentThings:FetchedResults<Thing>Where the .fetchRequest(matching: .recent) is producing a FetchRequest with Predicate and SortDescriptors.The problems start when I use this in MultiTasking mode on an iPad. The user adds new data to the App using a Share Extension.If I have the App side by side with another App that can share to it, the share is successful, I can see the data go into CoreData and the MasterListView re-draws by the logs but the actual data is not reliably refreshed.I have logging in the MasterListView to tell me when it re-draws and when it receives a Notification from the core data stack that there has been an update.The core data stack is running a NSPersistentHistoryChangeRequest, filtering out the added Thing successfully, so I know it is there.I have tried everything I can think of, including things like: NSManagedObjectContext.mergeChanges(fromRemoteContextSave:into:) viewContext.stalenessInterval = 0 viewContext.refreshAllObjects() viewContext.stalenessInterval = -1And everything else I have found on SO ;-)What am I missing?

Hi AllI am developing a CoreData + CloudKit App for iOS, based partly on the code in CoreDataCloudKitDemo.The intention of the App is that content will be used in the App but added from a Share Extension.The CoreData Store is configured to reside in a shared App Group.Addition and editing of content is functioning but I find that when new content is saved to CoreData from the Share Extension, data does not get pushed to CloudKit until the App itself is brought to the foreground. Which clearly is not the requirement.Saves made within the App itself eg. from an edit, are pushed to CloudKit immediately.How do I ensure this happens from the Share Extension?

I am writing a SwiftUI App in Xcode 12.0 beta (12A6159), the app is intended to work on iOS13.5 and up. I am instantiating ObservableObjects at one level of my View hierarchy in the View's init() function, passing them as appropriate using .environmentObject, then attempting to pick them up in @EnvironmentObject in Views several layers deeper. The consuming Views are getting the error: A View.environmentObject(_:) for ********* may be missing as an ancestor of this view. After careful testing, I find that the EnvironmentObjects are not being passed through NavigationLink. We already have the well known issue of these not being passed through .sheet presentation (a major inconvenience), now we are contending with the same issue with NavigationLink? Is this intentional or a bug? Is there a workaround? It is definitely not what I would consider my preferred design.

I am prototyping an iOS App in Swift Playgrounds. The App has Drag & Drop features internally using custom identifiers. The data that is being moved around is a struct that contains a deeplink URL that can be used to identify my models. I have three different entities to deal with. One is identified with a UTI com.example.item, the other two as com.example.collection. Items may be dropped onto Collections and visa versa, but the same type my not be dropped onto itself. For onDrag(_:) I produce an NSItemProvider and register the entity using registerDataRepresentation(forTypeIdentifier: visibility: loadHandler:). The ‘loadHandler’ encodes the URL of the entity as Data. I use the appropriate custom UTI String for the entity. So far so good, I can see that the right UTI String has been registered by examining the NSItemProvider. For onDrop(of:delegate:) I provide the valid UTI (this filter does not seem to be honoured) and a custom class implementing DropDelegate, giving it a reference to the entity at the drop target. As the filter does not seem to work, my DropDelegate implements func validateDrop(info: DropInfo) -> Bool. In this function, I attempt to filter which drops are valid by calling info.hasItemConformingTo(_:) and checking against the drop target. What I am finding is that even though I can see my custom UTI strings have been registered in the NSItemProviders, they are never visible when calling hasItemConformingTo(_:). In this situation I would be unable to implement performDrop AFAICS. I wonder if this problem is to do with my misunderstanding of how Drag & Drop works (I have also attempted other approaches like registering custom Objects with the NSItemProvider, but have the same problem. Is this possibly caused by my environment? As I am writing this prototype in Swift Playgrounds, where there is no Info.plist, so I am unable to register custom UTI schemes? Many thanks for any suggestions.

I have a CoreData model, in a Swift Package with tests. I can successfully run the tests, when I load the model using NSPersistentContainer, however attempting this with NSPersistentCloudKitContainer always fails in the call to loadPersistentStores(completionHandler block: @escaping (NSPersistentStoreDescription, Error?) -> Void) The error is : [CK] BUG IN CLIENT OF CLOUDKIT: Not entitled to listen to push notifications. Please add the 'aps-connection-initiate' entitlement. This issue is described on StackOverflow however, the accepted solution does not appear to work in my case. I have tried adding the aps-connection-initiate key to my App Info.plist, the Test Info.plist and the SPM bundle. No change. (NB. adding this to the entitlements file just breaks auto signing). I have enabled App entitlements for App Groups, Remote Notifications background mode, Push Notifications and iCloud CloudKit with a store identifier. I have checked my model. All relationships have inverses. No unique constraints, etc. etc. I am sharing a Bundle ID with a previous version of the App, that also uses CoreData+CloudKit, each version has it's own Model and container identifier, each container identifier is available in the provisioning profile. The new version of the model has two NSPersistentStoreDescriptions, one is configured for CloudKit, the other is a local cache. I am completely stuck, suggestions would be very welcome.

I am trying to render a list of entities that are split into sections (think CoreData NSFetchedResultsSectionInfo). This my solution, however it renders poorly. The ScrollView is far too long, scrolling is not fluid and may freeze. struct SectionsGridView: View { let results: Sections<ListItemViewModel> let columns = [ GridItem(.adaptive(minimum: .cellSize)) ] var body: some View { ScrollView { LazyVGrid(columns: columns, spacing: .gridSpacing, pinnedViews: .sectionHeaders) { ForEach(results) { section in Section(header: Text(section.title?.uppercased() ?? "error")) { ForEach(section) { item in GridCell().environmentObject(item) } } } } } } } private extension CGFloat { static let gridSpacing = 8.0 static let cellSize = 100.0 } I believe this solution (or very similar) used to be in the documentation. I have tried several ways of doing this, either I get the scrolling issue or pinnedViews won't pin.