Core Data & iOS5

[sneaky]

Just running the final tests on an app now and I've just started testing on iOS5.
I have been tweaking the Core Data performance all week under iOS4.3 and I've got it to a really sweet state now. So I'm pretty happy that my implementation is pretty good and solid at this stage.

Just started testing on iOS5 and the app is, not crashing but hanging, right left and center. I pause and it's almost always sitting on a ..execurefetchrequest. It never completes but is just hung.

I have several crashes as well. They are happening at different points for different reasons. As in the app can crash at the same spot 5 times and give 3-4 different reasons for it!

Also, trying to insert rows using a fetched results controller throws this:

CoreData: error: Serious application error.  An exception was caught from the delegate of NSFetchedResultsController during a call to -controllerDidChangeContent:.  Invalid update: invalid number of rows in section 0.  The number of rows contained in an existing section after the update (1) must be equal to the number of rows contained in that section before the update (0), plus or minus the number of rows inserted or deleted from that section (0 inserted, 0 deleted) and plus or minus the number of rows moved into or out of that section (0 moved in, 0 moved out). with userInfo (null)

This seems like a pretty fluffy request for help I do agree but this isn't confined to a single block of code or anything, everywhere throughout the app the app is either hanging or crashing on Core Data operations that worked really well on iOS4. Have anyone seen anything like this by any chance when upgrading from 4-5?

[BrianSlick]

Well, it says 0 inserted, 0 deleted. That's curious. How are you inserting the rows?

[sneaky]

Everything Core Data is being done in a singleton, all inserts of this type of data just use the one managedobjectcontext.

I tried to insert a bit of data in an init method of my singleton, then as soon as the UI load it calls for the data and the application deadlocks:

#0  0x94963876 in __psynch_mutexwait ()
#1  0x956dd6af in pthread_mutex_lock ()
#2  0x019f0c22 in -[_PFLock lock] ()
#3  0x019f0bfa in -[NSPersistentStoreCoordinator lock] ()
#4  0x01a08ed9 in -[NSPersistentStoreCoordinator executeRequest:withContext:error:] ()
#5  0x01a0706d in -[NSManagedObjectContext executeFetchRequest:error:] ()
   ...

I have been trying to init the managedobjectcontext with different concurrency types. This one here should mean that the context have the same behaviour as iOS4.

__managedObjectContext = [[NSManagedObjectContext alloc] initWithConcurrencyType:NSConfinementConcurrencyType];

[BrianSlick]

Why are you messing with concurrency?

[sneaky]

I've half figured it out. I'm actually working in different threads. Wasn't a problem under ios4 but it is now. I'm creating a new managedobjectcontext for each now and it's working better.

There is still a good bit of odd behaviour but I'm getting through it.

[BrianSlick]

That's how you were supposed to do it all along, but my understanding is that iOS 5 is meaner about enforcing it.