Array initialize causing crash in simulator, only with certain versions set

Question

I am initializing an array in my viewDidLoad method:
for (i=0; i<NUMBEROFIMAGES; i++) {
[buttonsArray addObject:[UIButton buttonWithType:UIButtonTypeRoundedRect]];
[[buttonsArray objectAtIndex: i] setImage:tmpImage forState:UIControlStateNormal];
There happens to be 28 images.
1. If I build in Xcode in v2.0, the app doesn't crash in the simulator, regardless whether the simulator is set to hardware v2.0 or v2.1, and regardless of whether NUMBEROFIMAGES set to 27 or 28.
2. But if I build in Xcode in v2.1 the result is different. The app still doesn't crash in simulator hardware v2.0 or 2.1 with NUMBEROFIMAGES set to 27. But it does crash upon startup when the simulator is set to hardware v2.1 when NUMBEROFIMAGES set to 28.
Anybody see anything like this happen?
One question I have about my loop. When creating arrays of objects manually (not in a loop) I had been adding one extra 'nil' object at the end.
I haven't been doing that when creating the array in a loop. After the loop do I need to add one more nil object?
Also, how do I keep the simulator set at hardware v2.1? It always seems to default to v2.0 when starting up.
Thanks!
doug

Answer 1

To set the default target in Xcode go to Project|Edit Project Settings. Click on the 'Build' tab. Find the Architectures section (it's first for me). Drop down the list for Base SDK. This will now be your default.
The Base SDK is set for 2.1. And in Xcode it does remain 2.1. The problem, though, is that the hardware version in the simulator when it runs always starts in 2.0 and I have to manually switch the simulator setting.
(pause to check something)
I thought there might be a simulator hardware version preference, but there isn't. Just the setting in the hardware menu.
As for the crash at 28 images. What's the error message? Any useful stack trace info in the console? What else in your code uses that value? Are you sure it is this loop that crashes and not some other code?
The error is TERMINATING_DUE_TO_UNCAUGHTEXCEPTION.
Up until now, that has invariably (no pun intended) meant an array out of bounds. There is a stack trace. Unfortunately, I don't really understand how to interpret them yet.
doug