nsmanagedobjectcontext

I have an app set up much like the iCloudCoreDataRecipes sample (ie, using Core Data in conjunction with iCloud). In the app delegate, I observe the NSPersistentStoreDidImportUbiquitousContentChangesNotification When a notification arrives, I call [context mergeChangesFromContextDidSaveNotification:note]; I have some additional processing I'd like to do when this notification is received but am having trouble using the objects identified by the NSManagedObjectID's present in the NSDeletedObjectsKey set. NSSet *deletedObjects = [info objectForKey:NSDeletedObjectsKey]; for (NSManagedObjectID

I have setup a Core Data app with the usual boilerplate code, and the RootViewController initializes the FRC by calling this: - (NSFetchedResultsController *)fetchedResultsController { if (__fetchedResultsController != nil) { return __fetchedResultsController; } // configure the fetchRequest, sectionKey and cacheName __fetchedResultsController = [[NSFetchedResultsController alloc] initWithFetchRequest: fetchRequest managedObjectContext: self.managedObjectContext sectionNameKeyPath: sectionKey cacheName: cacheName]; return __fetchedResultsController; } All the sample code I've seen does this.

NSManagedObject provides access to its NSManagedObjectContext , but does it retain it? According to "Passing Around a NSManagedObjectContext on iOS" by Marcus Zarra , "The NSManagedObject retains a reference to its NSManagedObjectContext internally and we can access it." How does Zarra know this and is he correct? I'm asking because I want to know if the NSManagedObjectContext will be dealloc 'ed in the tearDown method below. (I'm using CocoaPlant .) #import <SenTestingKit/SenTestingKit.h> #import <CocoaPlant/CocoaPlant.h> #import "AccountUser.h" @interface AccountUserTests : SenTestCase {

I have an app which is based on the Utility template (where you flip over the view to see another). On the first view there is a login screen, then it flips over to reveal a UITabBar style interface. I'm having trouble working out how to pass the managedObjectContext from the App Delegate (where it is created) all the way through to each of the Tab Bar's views. App Delegate's managedObjectContext get passed to FrontLoginViewController which gets passed to BackViewTabBarViewController .. where next? The BackViewTabBarViewController nib has a UITabBarController with a UINavigationController for

I expect (hope even) that this will be a stupid question, but after wrestling for many hours with this problem I need some insight. My iOS 5.1 app uses nested MOCs, having a PrivateQueueConcurrency child MOC, call it MOC-Child, whose parent is a MainQueueConcurrency MOC, call it MOC-Parent. MOC-Parent backs a table view that displays its entities. MOC-Child is used by a parser, which runs asynchronously on a non-main thread, to create new entities that correspond to XML entity-descriptions parsed from a URL connection, and then push the new entities to the MOC-Parent, via a save on the MOC

I don't understand the output of NSLog for the array returned by a NSFetchRequest. I'm reading my database and placing the contents in an array, looping through the array and then outputting the contents with NSLog. I don't quite understand the output in the log file. Code below: -(void)createXMLFeed{ //Fetch details from the database. NSFetchRequest *request = [[NSFetchRequest alloc] init]; NSEntityDescription *entity = [NSEntityDescription entityForName:@"Tabrss" inManagedObjectContext:managedObjectContext]; [request setEntity:entity]; NSError *error; self.stories = [[managedObjectContext

I was looking for posts regarding to this, but I don't fully understand... What is the difference between: [context reset]; and: for (NSManagedObjectID *objId in objectIds) { [context deleteObject:[context objectWithID:objId]]; } Or are they equivalent? Thanks Using reset puts the managed object context back to the state it was in when you first created it-- before you had performed any fetches, created any new objects, etc. If you have any managed objects in memory that were fetched from this context, they're now unusable. Using reset does not affect the persistent store file . All instances