Assertion failure on picker view

Question

I'm getting an assertion failure while scrolling a picker view w/ zero data(zero rows). While scrolling the picker view I'm getting this crash. Testing on iOS 6

* Assertion failure in -[UITableViewRowData rectForRow:inSection:], /SourceCache/UIKit_Sim/UIKit-2372/UITableViewRowData.m:1630

* Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'request for rect at invalid index path ( 2 indexes [0, 0])'

Any help is appreciable.

This actually just showed up for me when everyone started updating to iOS6. I had zero crashes related to this before the iOS release. — iwasrobbed, Oct 11 '12 at 11:06
I can confirm this is iOS 6 only. iOS 5 does not crash with an empty picker view. — Vinnie, Nov 05 '12 at 16:09
Phew. Aha.. I wondered why our app suddenly started crashing all over the place. Thanks above commenters for noticing! — Kalle, Nov 13 '12 at 22:19

score 39 · Accepted Answer · answered Oct 02 '12 at 03:30

39

I've the same problem

I don't know reason why it is happen,

but it can be fixed in ios6 (how it works in ios5 I didn't check):

- (NSInteger)pickerView:(UIPickerView *)pickerView numberOfRowsInComponent:(NSInteger)component
{
    if ([self getCount] == 0)
        return 1;
     return [self getCount];
}

- (UIView *)pickerView:(UIPickerView *)pickerView viewForRow:(NSInteger)row forComponent:   (NSInteger)component reusingView:(UIView *)view {
   if ([self getCount] == 0)
       return nil;
}

answered Oct 02 '12 at 03:30

INT

406
4
2

1

That did the trick, thanks ... weird, I wonder if it's a bug in the framework – Joel Martinez Oct 10 '12 at 20:12
It's gotta be... seems strange to have to return 1 when it's empty – iwasrobbed Oct 11 '12 at 14:54
@iWasRobbed did you get a chance to file a bug report for this ? – Manoj Nov 09 '12 at 11:20
This trick did not solve the crash in my App. My solution is to not present the pickerview when the datasource is empty. – djleop Dec 07 '12 at 08:12
As making row count always to at least 1, you can have side effects. So alternatively, you can also use picker.userInteractionEnabled=NO or YES in your data update code. – Kashif Hisam Apr 03 '13 at 12:05

score 0 · Answer 2 · answered Dec 06 '12 at 04:30

0

The answer is actually very simple! After having some trouble with this myself, I discovered that you must set the delegate and the dataSource to the view controller that the picker view is connected to.

answered Dec 06 '12 at 04:30

TheMlabTechGuy

47
4

1

With out delegate and datasource it will never ges into delegate methods of it. – Madhu Feb 20 '13 at 06:43

Assertion failure on picker view

2 Answers2

Linked