CoreData Exception: Could not fulfill a fault
CoreData Exception: Could not fulfill a fault
- Subject: CoreData Exception: Could not fulfill a fault
- From: "E. Wing" <email@hidden>
- Date: Thu, 22 Sep 2005 16:05:45 -0700
Hello, I have encountered a series of what seem to be CoreData bugs.
Because of these, I'm wondering what I need to investigate next in
order to develop a reliable workaround.
The bug of my main focus right now seems to be a notification bug
using NSManagedObjectContextObjectsDidChangeNotification. Under
certain conditions with undo/redo, I have found objects that should
marked as inserted (via NSInsertedObjectsKey) are not. I have just
filed a very detailed and elaborate bug report on this with example
code demonstrating the problem (Radar ID: 4268458).
I think I might be able to work around this as long as the deletion
notifications aren't missing as well. (So far I haven't encountered
this.) But sometimes when I continue to use my program after
encountering the notification bug, I notice that when I quit, I
receive the log message:
Exception raised during posting of notification. Ignored. exception:
CoreData could not fulfill a fault.
I'm nervous about this message because of another bug I hit a few days
earlier. I originally hit a "Could not merge changes" error when
saving. I saw that this bug was mentioned on the mailing list about a
month ago by Jesse Grosjean. I seemed to have hit it, though in a
slightly different way. But we both only have one managed object
context, so the CoreData troubleshooting guide about this error
doesn't apply to this specific case and it implies a CoreData bug. I
also just filed a detailed bug report on this too (Radar ID: 4269895).
I may have come up with a specific work around for my app for the
"Could not merge changes" error, but with this "Exception: CoreData
could not fulfill a fault" message, I'm wondering if I'm on a slippery
slope that will corrupt the CoreData state and lead me back to the
"Could not merge changes" error. This error is extremely bad because
once you hit it, you lose all your data because you can't save.
So to start with, I'm wondering what this exception means and how
worried I should be about seeing this. I'm also wondering if there is
something I should/can do to investigate this further. I don't have
any experience with dealing with this kind of message so I'm not sure
what to do.
Thanks,
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden