views:

25

answers:

2

Hi I have a simple database app on the iPhone that uses core data. I was just looking at some Flurry exception reports and I'm seeing the following error:

NSInternalInconsistencyException: no section at index 4

The number varies in the reports, but it is always the same message. Any idea on what this means and where to start my debugging efforts?

A: 

Where are you seeing this? Core Data would not throw errors across the network.

Marcus S. Zarra
If you setup an unhandled exceptions handlers in your app and pass it to Flurry analytics you see the unhandled exceptions that are created when people are running your app.TimestampErrorDetails08/07/10 10:24:14 EDT (1)NSInternalInconsistencyException: no section at index 7Msg: Crash!V: 3.0.1P: iPadE: Uncaught08/06/10 10:42:35 EDT (1)NSInternalInconsistencyException: no section at index 9Msg: Crash!V: 3.0.1P: iPadE: Uncaught08/06/10 10:40:04 EDT (1)NSInternalInconsistencyException: no section at index 2Msg: Crash!V: 3.0.1P: iPadE: Uncaught
agilpwc
I would check your iTunesConnect account and look for proper crash logs. That will tell you exactly where it is crashing.
Marcus S. Zarra
A: 

It probably means that you have a tableview which is asking for a non existent section. Most likely, you are returning incorrect values from numberOfSectionsInTableView: for some reason.

TechZen
I would agree, that is the only thing that sounds close.
Marcus S. Zarra