TERMIN ... UNDUE EXCEPTION ... ??

m0s · 04-13-2009, 01:53 PM

OK.

So randomly while coding I get a crash and 'terminating due to uncaught exception', and I have no idea really what happened as I was just doing some tweaking.

Basically what I thought I would do is that I regularly zip up my development directory incrementally so that I can back track through the development process should disaster occur.

Fortunately I had backed up a day ago, and I had only been working on a small part of code, so I thought I would copy/paste the new code into textedit, then delete the contents of my current project directory and reinstate it from the zip file I made a day ago.

But this old project, which had been working on just fine until 20 minutes ago, and certainly was not crashing when I zipped it up yesterday is ALSO crashing with an uncaught exception.

Advice Please - Thanks.

here is the exception

Code:

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)'

m0s · 04-13-2009, 01:57 PM

ha ha fixed it.

smithdale87 · 04-13-2009, 02:03 PM

what turned out to be the problem??

**Kalimba** · 04-13-2009, 02:04 PM

Quote:

Originally Posted by m0s

Code:

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)'

The exception message is telling you right there what the problem is. You're indexing an array with index of 1, but the array only contains one object. Run it in the debugger to find out exactly where this is happening.

m0s · 04-13-2009, 02:14 PM

Quote:

Originally Posted by smithdale87

what turned out to be the problem??

By "fixed it" I meant "oops I broke it" and reset the simulator.

Quote:

Originally Posted by Kalimba

The exception message is telling you right there what the problem is. You're indexing an array with index of 1, but the array only contains one object. Run it in the debugger to find out exactly where this is happening.

Right, not so sure but I think it is to do with my Picker, I was being a little heavy handed with it so I think the picker might have been out of bounds(?). I am saving the picker position in NSUserDefaults so that on next boot the app goes to the last position the picker was in.

The only time I could recall there being an ObjectatIndex call in my code was to do with the picker, so I figured it was a problem during the reset to previous at boot. So I figured resetting the Simulator -> Losing the NSUserdefaults would fix it.

I realize this isn't a long term solution, and it's actually good to have found the bug now rather than later, but I am just glad it is working again.

I have heard about and experienced some odd behavior from pickers, with individual picker entries occasionally dropping out. Not sure what causes it, or if anyone here has experienced it.