That error is most likely coming from a NSFetchedResultsController that has a released delegate. Do you have a UIViewController that you released and didn't release the associated NSFetchedResultsController?
Thanks for the response Marcus. My NSFetchedResultsControllers are synthesized properties of their UITableViewControllers. In the viewDidUnload method I have self.
FetchedResultsController = nil to relinquish ownership. Do I also need to release fetchedResultsController in dealloc as well? – Max Clarke Aug 20 '10 at 17:11 Yes, any property that is set as retain must be released in the -dealloc.In fact, I would highly recommend setting all properties to nil even if they are just ascom/questions/5179071/… – Csabi Mar 3 at 14:26.
Even I faced the same issue. But for iOS 4.2 the problem is NSError is unitialised, so it is treated as garbage and while updating/inserting we have if (!managedObjectContext save:&error) { NSLog(@"Unresolved error %@, %@", error, error userInfo); exit(-1); } So in save the iOS treats the error as garbage and so the exception. Try to initialize it to nil.It solved my problem.
The issue is seen only with 4.2iOS.
Added rooms simply appear with a default "New Room" name in the table. The second view is a list of Scenes in the selected room. Same deal here, you can delete and add Scenes, and added Scenes simply appear in the table with the name "New Scene".
Nothing special really. I'm using a FetchedResultsController in both view controllers, with the Scenes one having an NSPredicate to return only scenes from the selected room. I'm also using the controllerWillChangeContent, controllerDidChangeContent etc. delegate methods for the table view updates.
This all works fine at first, but usually after navigating around rooms and scenes then trying to delete a scene it will crash. It will inevitably crash if you play around with it long enough. It only happens when deleting a scene.
If you press the edit button and delete a scene and it works, then all the following deletes in that edit session will always work. It will only ever crash on the first delete of the edit session.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.