On 2013 Jun 17, at 00:17, Michael Crawford wrote:
> Try adding assertions throughout your code.
That's a good idea, Michael, although for Release builds I prefer to just
NSLog(). My "Trouble Zipper" that users can download from the app's Help menu
filters out system logs. Not sandboxed :)
Try adding assertions throughout your code.
I get the most mileage by validating the input parameters to all my
subroutines. If one of your parameters is a pointer, can it be nil?
Less commonly I validate return results and side effects.
Also look through all of your subclass method overrides,
On 2013 Jun 16, at 22:22, Julian Richardson wrote:
> I believe that ALAssetLibrary uses Core Data, so the problem could be a
> user's messed up image library.
Thank you, Julian. I don't think that's the problem here. The error logged
indicates that the object's entity is one of "my" entitie
ityForName:inManagedObjectContext:].
>
> 2. Managed object's context was accessed from multiple threads. Maybe an
> updating thread got ahead of the inserting thread somehow? That would be
> weird.
>
> Are there any other causes of "Cannot update object th
Maybe an
updating thread got ahead of the inserting thread somehow? That would be weird.
Are there any other causes of "Cannot update object that was never inserted"
that I should be looking for?
Thank you,
Jerry Krinock
___
Cocoa-dev mailin
