I've got a line of code that works fine in sim but not on iPhone

[skinrock]

// Default settings
NSString *var1 = [NSString stringWithString:@"YES"];
NSString *var2 = [NSString stringWithString:@"40.0"];
NSString *var3 = [NSString stringWithString:@"YES"];
NSString *var4 = [NSString stringWithString:@"40.0"];
NSString *var5 = [NSString stringWithString:@"NO"];
NSString *var6 = [NSString stringWithString:@"5.0"];
	
// Register initial default settings
NSDictionary *appDefaults = [[NSDictionary alloc] initWithObjectsAndKeys:var1, @"Var1", var2, @"Var2", var3, @"Var3", var4, @"Var4", var5, @"Var5", var6, @"Var6"];

Ignore the naming, it's just to protect my code. Basically I'm using YES and NO for BOOL vars, because when you fetch it as a BOOL, it can use a string and use YES or NO to determine the value of the BOOL. The other ones are floats, same thing...it can pull a float from a string.

This works fine in the sim, I can register this array and write to it...everything works as expected. In my iPhone, it crashes...and it has nothing to do with the UserDefaults stuff...it's that dictionary...if I try to create it on the iPhone...it crashes.

[skinrock]

Okay, turns out that exact code doesn't work in the sim, but what does work is if I create the strings like so:

NSString *var1 = @"YES";

That works fine, and still doesn't work in the iPhone.

[skinrock]

Interesting, I added nil to the very end of my key/object pair list, and that fixed it. I have an app that is currently for sale that didn't need the "nil" part...I only had two key/object pairs, but it would be odd that the number of pairs has an effect.

[Kenrik]

Arrays need the "nil" at the end to function properly.

glad you found the issue.

[skinrock]

Ya, I remember seeing it, which is the only reason I thought of it...but I was hesitant because like I said, I have another app where it didn't affect it. Oh well, time for bed.

[PhoneyDeveloper]

The nil at the end of the list is required by the api as indicated by the method prototype:

- (id)initWithObjectsAndKeys:(id)firstObject, ... NS_REQUIRES_NIL_TERMINATION;

If you left it out and it didn't crash that was just luck.