nsfetchedresultscontroller

I've been trying to build a Core Data stack as described by Marcus Zarra , where he has a Private Queue context and a Main Queue context (where the Main Queue context is a child of the Private Queue context). I believe I've correctly rebuilt ( here ) his described MCPersistenceController faithfully in Swift (the example code was Obj-C). The problem is in my ListViewModel class (which contains an NSFetchedResultsController ). No matter what I try, its delegate callbacks ( controllerDidChangeContent etc) don't get called when a new Item object is inserted. The FRC and NSFetchRequest use the Main

I have UITableView with NSFetchedResultsController NSFetchedResultsController *aFetchedResultsController = [[NSFetchedResultsController alloc] initWithFetchRequest:[self dataFetchRequest] managedObjectContext:[MLCoreDataService sharedInstance].managedObjectContext sectionNameKeyPath:@"checked" cacheName:nil]; aFetchedResultsController.delegate = self; I've implemented - (void)controller:(NSFetchedResultsController *)controller didChangeObject:(id)anObject atIndexPath:(NSIndexPath *)indexPath forChangeType:(NSFetchedResultsChangeType)type newIndexPath:(NSIndexPath *)newIndexPath { UITableView

Refactored to vanilla UIViewController Rather than having the UITableView toggle between active and inactive UISearchController , I refactored to a vanilla UIViewController with a UISearchBar at the top and a UITableView directly underneath it. What I'm trying to do is toggle the fetchedResultsController between having a predicate which is set by the text in the searchBar and one that grabs everything. I found this answer, which describes a solution to a similar problem in Objective-C and served as the basis upon which I refactored my Swift project: How to filter NSFetchedResultsController

I have an operation object which creates it's own Managed Object Context. The operation object performs calculation basically to take off load from main thread while main thread concentrates on the UI aspect. This operation object's MOC shares a common persistent store across the application. It sometimes happens such that, while the operation is being performed, the MOC of main thread is notified of changes in backend. So, I try to merge the changes of MOC, where some of the deletions in model objects might happen. In some rare cases, as I observe, the operation object might not have been

I can't figure out why, for the life of me, the NSFetchedResultsControllerDelegate methods are not firing when I add data to the underlying datastore. The data shows up immediately if I restart the iPhone application. I have subclassed UITableViewController and conform to NSFetchedResultsControllerDelegate: @interface ProjectListViewController : UITableViewController <NSFetchedResultsControllerDelegate> { NSFetchedResultsController* fetchedResultsController_; NSManagedObjectContext* managedObjectContext_; } I instantiate the NSFetchedResultsController and set the delegate to self: //

I have an NSFetchedResultsController and a few operations that inserts and updates managed objects on separate threads via NSOperationQueue. The FRC looks like this, note that I have set the cache to nil: [NSFetchedResultsController deleteCacheWithName:nil]; NSFetchedResultsController *aFetchedResultsController = [[NSFetchedResultsController alloc] initWithFetchRequest:fetchRequest managedObjectContext:managedObjectContext sectionNameKeyPath:nil cacheName:nil]; Each threaded operation has its own managed object context and fires mergeChangesFromContextDidSaveNotification to the main MOC each