Hi Charles, I’m reading your comment and that’s exactly what I’m trying to figure it out. Did you find any solution to manage the problem?

I have implemented the same solution for one of my UITableView which queries a lot of data through Core Data for every UITableViewCell. There’s one missing piece to my solution though. I was wondering if you had an idea how to solve this.

So like I said, I implemented the same approach as you did but the difference is that, for example, when I call a function like self.model.textForIndexPath(indexPath), my model asks its NSFetchedResultController for the objectAtIndexPath and the returns me the text. The thing is that the NSFetchResultsController was initialized with a NSManagedObjectContext that was itself initialized with a private queue (NSPrivateQueueConcurrencyType).

This means that the NSOperationQueue we created for every UITableViewCells are trying to access objects in a NSManagedObjectContext that was not initialized on the same thread. This throws an exception as NSManagedObjectContext and NSManagedObject are not thread same and they shouldn’t be initialized in one thread and accessed from a different thread. Do you have any idea for a solution?

Thanks