Geek asks and answers

Getting serious application error with master data

The following error occurred while deleting an object from my application. Any ideas on how to fix this?

I'm still trying to recreate the process to find out exactly where it is crashing.

Serious application error.  Exception was caught during Core Data change processing.  This is usually a bug within an observer of NSManagedObjectContextObjectsDidChangeNotification.  CoreData could not fulfill a fault for '0x5adc8b0 <x-coredata://2B90C6EC-E046-4508-A1B1-6C4B19BF830D/Session/p1>' with userInfo {
NSAffectedObjectsErrorKey =     (
        "<Session: 0x6f7c830> (entity: Session; id: 0x5adc8b0 <x-coredata://2B90C6EC-E046-4508-A1B1-6C4B19BF830D/Session/p1> ; data: <fault>)"
    );
*** Terminating app due to uncaught exception 'NSObjectInaccessibleException', reason: 'CoreData could not fulfill a fault for '0x5adc8b0 <x-coredata://2B90C6EC-E046-4508-A1B1-6C4B19BF830D/Session/p1>''
+3
source share
2 answers

A) If you sign up to save notifications, Core Data indicates a failure there.

B) The message “cannot make an error” is often associated with deleting an object, after which some other part of your application tries to access any property. Yes, even those where errors were made earlier. The entire object is not applicable after deletion.

+3
source

, NSOperation. NSOperation " ", , . , "CoreData ". , " " " " , , NSOperation. NSOperation , . . ( .)

0

More articles:


All Articles