NSFetchedResultsController objectAtIndexPath crash (EXC_BAD_ACCESS)?

I think I see the problem. In your NSArrayToDataTransformer you have this: (id)reverseTransformedValue:(id)value { NSArray *array = NSKeyedUnarchiver unarchiveObjectWithData:value; return array autorelease; } Since unarchiveObjectWithData: does not begin with "alloc", "new", "copy", or "mutableCopy", you do not own the object and therefore may not autorelease it. You have the same problem in your NSDictionaryToDataTransformer.

I think I see the problem. In your NSArrayToDataTransformer, you have this: - (id)reverseTransformedValue:(id)value { NSArray *array = NSKeyedUnarchiver unarchiveObjectWithData:value; return array autorelease; } Since unarchiveObjectWithData: does not begin with "alloc", "new", "copy", or "mutableCopy", you do not own the object and therefore may not autorelease it. You have the same problem in your NSDictionaryToDataTransformer.

Yeah! I forgot about the fact that I can't release objects that I don't own. And now it's working!

Thank you, thank you thank you! :) I'll give you +50 after 19h :/ – Kashiv May 8 at 13:39.

Your inclusion of the value transformers into the class and the using +initialize is non-standard. Although +initialize should work, it is recommended in the Core Data docs not use any kind of initialization methods at all but to rely on awakeFromFetch for initialization. I would check your tableview methods such as numberOfRowsInSection: to ensure you are getting the right indexes back from the tableview.

If the rows in the tableview and the count of the fetchedObjects array come out of sync, you can get this kind of crash.

And there's a problem, because fetchedResultsController returns the real number of rows. NSManagedObject crashes my app. I'll check awakeFromFetch method and write the result.

– Kashiv May 3 at 22:35 Nope... Same result. I'll post my Faktura object insertion code. Maybe there's a problem.

– Kashiv May 4 at 13:29.

In a UITableViewController, I use an NSFetchedResultsController for my data. Everything works fine, except for when I start importing some objects in a separate thread: I use an NSOperationQueue in which I insert objects into my ManagedObjectContext. This happens in a separate view.

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.

Related Questions