B) Why is something flushing caches on the parent object when the child object saves? This certain SOUNDS like it could be what's screwing up my parent editing context's snapshot.
directly above that, it calls: final NSArray deletedObjectsToFlushInParent = ERXEOControlUtilities.localInstancesOfObjects(parentEC, ec.deletedObjects()); ... anyone know if there is there anything weird about performing this operation in editingContextWillSaveChangeson a pending delete from a child to a parent? Mark -- you might checkout the Wonder source and comment that block of code just to try. I don't think it will have any affect, but who knows.
Also, if you don't have this in a nested EC, and just delete them directly, does it still fail? (not that this will solve your problem, but it might narrow down possible failure points)
Do you ever invalidate EO's? I notice in some source you posted before that you have a refresh() method that invalidates the EO. Does this only get called during handling an EOGeneralAdaptorException, or possibly somewhere else also? Calling invalidate deletes snapshots and can /potentially/ cause a problem like what you're seeing.
Oh, and how exactly are you creating your two editing contexts? Can you post that code just for completeness?
ms |