> One of the other things I had been working on must have fixed the underlying
> problem, and my implementation of identifier and setIdentifier were actually
> causing this issue. I completely removed those two methods (which is of
> course going directly against the documentation at the top of
Thanks Ben
One of the other things I had been working on must have fixed the underlying
problem, and my implementation of identifier and setIdentifier were actually
causing this issue. I completely removed those two methods (which is of course
going directly against the documentation at the top
That particular function is trying to CFRetain the result of -identifier on
your store. If you've overridden it, make sure it never returns nil and it
always returns the same UUID at least until someone calls -setIdentifier. The
UUID should also be set in the store's metadata with the key NSSto
I think I've narrowed it down a bit - it is now to the stage where the crash is
at:
#0 0x7fff80ddf788 in CFRetain ()
#1 0x7fff874ed6ad in +[NSTemporaryObjectID classForStore:] ()
#2 0x7fff874ed352 in _PFFastStoreTemporaryIDClass ()
#3 0x7fff874ed2f8 in -[NSTemporaryObjectID _s
Finally some progress. I found that the error message I was getting appeared to
be a total red herring, and eventually tracked it down to an issue that
appeared to be happening during the store migration, where it would have a
validation error against a mandatory attribute which I normally set l
Thanks for that suggestion Ben - I haven't come across that method of debugging
before. I tried doing it based on the address that I got from the stack trace,
but I just seem to get the things relevant to the NSNumber:
$ /Developer/usr/bin/malloc_history 12908 0x100e00860
ALLOC 0x100e00860-0x10
> Further information: I have just gone through every place in our code where
> it makes reference to the managed object context (there's only 90 of them
> thank goodness), and there is nothing there where we either retain or release
> a managed object context, or use one in a notification or an
Further information: I have just gone through every place in our code where it
makes reference to the managed object context (there's only 90 of them thank
goodness), and there is nothing there where we either retain or release a
managed object context, or use one in a notification or anything l
Having sorted out the problem that occurred when I closed files, I am now back
to the "save as" issue (I was hoping that the two problems were related, but
apparently not). I have reverted to using a stock standard
NSManagedObjectContext I still haven't a clue where to look to debug this.
Runni
