• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Default Core Data errors
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Default Core Data errors


  • Subject: Re: Default Core Data errors
  • From: Rick Mann <email@hidden>
  • Date: Wed, 14 Oct 2009 12:21:47 -0700

In the simplest case, I don't create any entities. I don't override any of NSPersistentDocument's persistence-related methods. I just save the new untitled document, then try to re-open it.

On Oct 14, 2009, at 12:11:29, Ben Trumbull wrote:

Do you check, and at least assert, if any API that has an NSError** parameter returns one ? (typically a return value of NO or nil). For Core Data, you'll always want to check adding a store to the coordinator, saving, and fetching. For your documented based app, the NSDocument APIs can also return errors.

When you get an NSError, you'll want to also log its userInfo dictionary.

- Ben


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Default Core Data errors
      • From: Ben Trumbull <email@hidden>
References: 
 >re: Default Core Data errors (From: Ben Trumbull <email@hidden>)

  • Prev by Date: re: Default Core Data errors
  • Next by Date: re: CoreData could not fulfill a fault after Save As
  • Previous by thread: re: Default Core Data errors
  • Next by thread: Re: Default Core Data errors
  • Index(es):
    • Date
    • Thread