CoreData unresolved keypath after save
CoreData unresolved keypath after save
- Subject: CoreData unresolved keypath after save
- From: Noah Lieberman <email@hidden>
- Date: Fri, 28 Jul 2006 11:53:13 -0700
Hello,
I've done some digging with little luck so far, so hoping someone on
the list may have run across this:
I've got a CoreData app, works fine on initial document creation, but
after a save I get the old
"NSRunLoop ignoring exception 'unresolved keypath: flightDate' that
raised during posting of delayed perform with target 17afc250 and
selector 'invokeWithTarget:'"
I'm a bit stumped, because if the key didn't exist or something was
set up wrong in the nib then why does it work before the save?
I've gone through the nib and the code carefully and don't see any
obvious typos or anything, again it shouldn't work at all if this
were the case. I'm looking for any clues as to where to look. It
seems that the fact that it only happens when trying to load a saved
file (which has the "flightDate" field set) causes the issue is
significant, I'm just not sure of what! I can set flightDate all I
want on a new document...
Thanks,
Noah
_______________________________________________
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