Not as I recall, but it's worth noting that isDeleted only returns YES between the time that a managed object is marked for deletion, and when that change is committed. After that, it returns NO (which kind of sucks). The managedObjectContext will also be nil at that point (though that CAN happen in other circumstances).
On Fri, Mar 7, 2014 at 2:47 PM, Rick Mann <[email protected]> wrote: > > On Mar 7, 2014, at 13:44 , Sixten Otto <[email protected]> wrote: > > > FWIW: trying to access a managed object that has been deleted, but to > which something still has a reference, can produce symptoms like the second > kind of access you describe. > > Even the isDeleted property? > > > > > Sixten > > > > > > On Fri, Mar 7, 2014 at 2:21 PM, Rick Mann <[email protected]> wrote: > > It seems that objects can be faulted in two ways. In the first, an > access will load the data and things are fine. In the second, an access > results in a crash because the fault could not be fulfilled. > > > > Is there a way to tell these two apart? > > > > -- > > Rick > > > > > > > > > > _______________________________________________ > > > > Cocoa-dev mailing list ([email protected]) > > > > 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: > > https://lists.apple.com/mailman/options/cocoa-dev/himself%40sfko.com > > > > This email sent to [email protected] > > > > > -- > Rick > > > > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
