Why does SSManagedViewController needs mainQueueContext to init?

[nitriques]

I ran against this nasty bug in my app.

- (NSFetchedResultsController *)fetchedResultsController always returns nil.

If I removed the [SSManagedObject hasMainQueueContext] check here everything works fine and the mainQueueContext gets created when the fetchRequest gets created.

Any ideas why ? Should I just called [SSManagedObject mainQueueContext] in my app delegate ?

[soffes]

This is intentional. If you are tearing down Core Data, your view controllers could touch a FRC and start up Core Data again. The desired way to get going is to reference mainQueusContext in application did finish launching.

I agree that this is a bit unexpected at first. I should document this a bit more.

Sam

On Mar 23, 2014, at 11:58 AM, Nicolas Brassard notifications@github.com wrote:

I ran against this nasty bug in my app.

• (NSFetchedResultsController *)fetchedResultsController always returns nil.

If I removed the [SSManagedObject hasMainQueueContext] check here everything works fine and the mainQueueContext gets created when the fetchRequest gets created.

Any ideas why ? Should I just called [SSManagedObject mainQueueContext] in my app delegate ?

—
Reply to this email directly or view it on GitHub.

[nitriques]

Ok thanks for the reply, I now know that my technique is not a hack and feel safer with it.

#22 will take care of documentation right ;) ? Thanks again for allowing others to build upon your work.