Re: CoreData unresolved keypath after save

Subject: Re: CoreData unresolved keypath after save
From: George Orthwein <email@hidden>
Date: Mon, 31 Jul 2006 13:07:14 -0400
Delivered-to: email@hidden
Delivered-to: email@hidden

Does this happen with new saved files or are you opening a saved doc from a previous version? (i.e. did you just add the flightDate attribute?)

If the latter, the result here would apply: http://www.google.com/search?hl=en&q=NSRunLoop+ignoring+exception+% 27unresolved+keypath&btnG=Google+Search

If the former... I dunno. :)

George


_______________________________________________
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


Follow-Ups:

Re: CoreData unresolved keypath after save
From: Noah Lieberman <email@hidden>


References:  
  >CoreData unresolved keypath after save (From: Noah Lieberman <email@hidden>)




Prev by Date:
Keeping an App Alive

Next by Date:
Re: Core Recipes question (Migration)

Previous by thread:
CoreData unresolved keypath after save

Next by thread:
Re: CoreData unresolved keypath after save

Index(es):

Date
Thread













  
   Home
   Archives
   Terms/Conditions
   Contact
   RSS
   Lists
   About
 






Visit the Apple Store online or at retail locations.

1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2011 Apple Inc. All rights reserved.

References:
	>CoreData unresolved keypath after save (From: Noah Lieberman <email@hidden>)