Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Cryptic error from Core Data: NSInvalidArgumentException, reason: referenceData64 only defined for abstract class

I'm doing an iPhone app that reads data from XML file, turn them into Core Data Managed Objects and save them.

The application is working fine, mostly, on smaller data set/XML that contains ~150 objects. I said mostly because 10% of the time, I'd get the following exception from CoreData while trying to save the context:

* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -_referenceData64 only defined for abstract class. Define -[NSTemporaryObjectID_default _referenceData64]!'

On a bigger data set (~2000), this happens every time, but not on the same place. It could fail on the 137th record, 580th, or the very last one. I've tried moving the save point (per object, per 10 objects, save once all objects are alloc/init'ed) but I always hit the exception above.

I've googled the exception and saw someone having the same issues but didn't see any resolutions.

My next step was going to be simplifying the managed objects and relationships to a point where this error stops and build from there to isolate the issue. The last resort is to ditch Core Data and just directly store into sqllite.

Thanks for all your help!

like image 653
Brombie Avatar asked Jan 05 '10 21:01

Brombie


2 Answers

I have the same issue. It works for smaller data sets, but for larger sets I get "_referenceData64 only defined for abstract class" errors. There's no abstract entities in my model.

EDIT:

I think I got this resolved. The issue in my case was a confusion on my part re threads. Here's the guidelines I followed to fix it:

  1. I parse XML data in a thread. On launching said thread, create a new NSManagedObjectContext using the same persistent store coordinator as your main thread's NSManagedObjectContext.
  2. Any new objects you make in your thread should be made for the thread's NSManagedObjectContext. If you have to copy over objects from the main thread's NSManagedObjectContext, copy over by ID. I.e.
    NSManagedObjectID *objectID = [foo objectID];
    FooClass *newFoo = [(FooClass*)[threadManagedObjectContext objectWithID:objectID] retain]
  3. When finished parsing, you need to save the changes made to the thread's NSManagedObjectContext. You must lock the persistent store coordinator. I used the following (incomplete code):

`

 - (void)onFinishParsing {     // lock the store we share with main thread's context     [persistentStoreCoordinator lock];      // save any changes, observe it so we can trigger merge with the actual context     @try {       [threadManagedObjectContext processPendingChanges];     }     @catch (NSException * e) {       DLog(@"%@", [e description]);       [persistentStoreCoordinator unlock];     }     @finally {       // pass     }      NSNotificationCenter *dnc = [NSNotificationCenter defaultCenter];     [dnc addObserver:self selector:@selector(threadControllerContextDidSave:) name:NSManagedObjectContextDidSaveNotification object:threadManagedObjectContext];     @try {       NSError *error;       if (![threadManagedObjectContext save:&error]) {         DLog(@"%@", [error localizedDescription]);         [persistentStoreCoordinator unlock];         [self performSelectorOnMainThread:@selector(handleSaveError:) withObject:nil waitUntilDone:NO];       }     } @catch (NSException *e) {       DLog(@"%@", [e description]);       [persistentStoreCoordinator unlock];     } @finally {       // pass     }     [dnc removeObserver:self name:NSManagedObjectContextDidSaveNotification object:threadManagedObjectContext];      [self performSelectorOnMainThread:@selector(parserFinished:) withObject:nil waitUntilDone:NO];   }    // Merging changes causes the fetched results controller to update its results   - (void)threadControllerContextDidSave:(NSNotification*)saveNotification {     // need to unlock before we let main thread merge     [persistentStoreCoordinator unlock];     [self performSelectorOnMainThread:@selector(mergeToMainContext:) withObject:saveNotification waitUntilDone:YES];   }    - (void)mergeToMainContext:(NSNotification*)saveNotification {     NSError *error;     [managedObjectContext mergeChangesFromContextDidSaveNotification:saveNotification];     if (![managedObjectContext save:&error]) {       DLog(@"%@", [error localizedDescription]);       [self handleSaveError:nil];     }   }   

`

like image 176
Adriaan Tijsseling Avatar answered Oct 05 '22 23:10

Adriaan Tijsseling


You have to follow the rule:

NSManagedObjectContext must be created on the same thread which uses it. (OR in other words, every Thread must have its own MOC)

Violation of above rule cause the following exception:

  • Exception in *** -_referenceData64 only defined for abstract class. Define -[NSTemporaryObjectID_default _referenceData64]!,

Another problem somebody might face is, if using the NSFetchedResultsController, the delegates will not be called on the UI classes.

I hope this answer will help someone!

like image 38
Ansari Avatar answered Oct 05 '22 23:10

Ansari