'+entityForName: nil is not a legal NSManagedObjectContext parameter - Core Data
Solution 1
If you are using segues you will get the same problems if you don't pass the context down the line. Use this code in the prepareForSegue method of class initiating the segue:
[[segue destinationViewController] setManagedObjectContext:self.managedObjectContext];
That assumes you hold your context in a property called "managedObjectContext" of course.
Solution 2
I had forgotten to pass the context to the view controller. Rookie error.
Solution 3
You can pass the context by including the following code before you begin to fetch the data form the database:
AppDelegate *appDelegate = (AppDelegate *)[[UIApplication sharedApplication]delegate];
context = [appDelegate managedObjectContext];
Solution 4
you should add this to your viewController:
id delegate = [[UIApplication sharedApplication] delegate];
self.managedObjectContext = [delegate managedObjectContext];
Solution 5
I got this problem and a colleague helped me out. If you got this error message: "entityForName: nil is not a legal NSManagedObjectContext parameter searching for entity name". And you made changes in you coredata model. I think the problem might not be the code.
The solution can be simple. Try one of those options:
- Just delete the app from the device you are testing, it should have the old version of your model.
- Create another database version using Xcode, >Editor>Add Model Version.
Hope it helps.
Alex Godbehere
Hobbyist Programmer. Studying Systems Engineering at University of Sheffield.
Updated on July 05, 2022Comments
-
Alex Godbehere almost 2 years
I have added all of the relevant code to the App Delegate, and I am able to add to the data model and fetch from the data model in applicationDidFinishLaunchingWithOptions.
My problem comes when I am trying to write to the data model in my View Controller. I have added this code to the header file:
NSFetchedResultsController *fetchedResultsController; NSManagedObjectContext *managedObjectContext; @property (nonatomic, retain) NSFetchedResultsController *fetchedResultsController; @property (nonatomic, retain) NSManagedObjectContext *managedObjectContext;
And this code to my implementation file:
NSManagedObjectContext *context = [self managedObjectContext]; NSManagedObject *model = [NSEntityDescription insertNewObjectForEntityForName:@"Events" inManagedObjectContext:context]; [model setValue:@"Sample Event" forKey:@"eventName"]; NSError *error; if (![context save:&error]) { NSLog(@"Couldn't save: %@", [error localizedDescription]); }
However, I get the following error:
'NSInvalidArgumentException', reason: '+entityForName: nil is not a legal NSManagedObjectContext parameter searching for entity name 'Events''
Does anyone know what's going on? Any help would be appreciated.
-
RyanG over 11 yearsThanks for this nice little snippet.. I can never remember the full syntax!
-
Syed Asad Ali over 9 yearsand this is the way to pass context to the view controller: AppDelegate *appDelegate = (AppDelegate *)[[UIApplication sharedApplication]delegate]; context = [appDelegate managedObjectContext];
-
LE SANG almost 9 yearsI set it to _managedObjectContext and it crashes. self.mangeObjectContext solve it. Thanks!
-
Tim almost 9 yearsGlad it works! I believe that, post Xcode 4.4, if you just use "@synthesize myProperty;" the compiler creates an instance variable called "myProperty" rather than "_myProperty". If you don't use "@synthesize" at all you get "_myProperty". So "_managedObjectContext" may not actually exist. I don't know because I can't see you code. "self.managedObjectContext" is safe because that calls the accessor as it always has.