This is weird but I'm getting used to that. Xcode is all uptodate and I can run my app on the simulators for iphone5 iphone6+ iphone6s iphone6s+ but not for the iphone6 odd! errors shown are 2016-03-08 12:53:34.974 nzpif2[8394:2480370] -[NSDecimalNumber isEqualToString:]: unrecognized selector sent to instance 0x7fa338427b10 2016-03-08 12:53:34.980 nzpif2[8394:2480370] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSDecimalNumber isEqualToString:]: unrecognized selector sent to instance 0x7fa338427b10' *** First throw call stack: ( 0 CoreFoundation 0x0000000111ef0e65 __exceptionPreprocess + 165 1 libobjc.A.dylib 0x0000000111969deb objc_exception_throw + 48 2 CoreFoundation 0x0000000111ef948d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 3 CoreFoundation 0x0000000111e4690a ___forwarding___ + 970 4 CoreFoundation 0x0000000111e464b8 _CF_forwarding_prep_0 + 120 5 nzpif2 0x000000010d4c0d7d -[BT_screen_htmlDoc viewDidLoad] + 7565 6 UIKit 0x000000011005af98 -[UIViewController loadViewIfRequired] + 1198 7 UIKit 0x000000011005b2e7 -[UIViewController view] + 27 8 nzpif2 0x000000010d4a8c1e -[BT_application buildInterface] + 4222 9 nzpif2 0x000000010d4bbb21 -[BT_loadConfigDataViewController configureEnvironmentUsingAppData:] + 1889 10 nzpif2 0x000000010d4bb2b2 -[BT_loadConfigDataViewController loadAppData] + 3042 11 Foundation 0x0000000111440b89 __NSFireDelayedPerform + 402 12 CoreFoundation 0x0000000111e50c84 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 13 CoreFoundation 0x0000000111e50831 __CFRunLoopDoTimer + 1089 14 CoreFoundation 0x0000000111e12241 __CFRunLoopRun + 1937 15 CoreFoundation 0x0000000111e11828 CFRunLoopRunSpecific + 488 16 GraphicsServices 0x0000000112b79ad2 GSEventRunModal + 161 17 UIKit 0x000000010fec4610 UIApplicationMain + 171 18 nzpif2 0x000000010d4b6ca4 main + 68 19 libdyld.dylib 0x0000000115a3b92d start + 1 20 ??? 0x0000000000000001 0x0 + 1 ) libc++abi.dylib: terminating with uncaught exception of type NSException (lldb) I can see that supportedInterfaceOrientationsForWindow is run just before hand but the error doesn't seem to be in there. I only have 2 plugins: * bt_screen_htmlDoc * menu_with_image Screenshot: https://cloudup.com/iXa0XPDhGoS/f Looking through the debug messages it could be happening somewhere between setting up the second tab button and the third. Both are valid in the config or it wouldn't work on the other versions but it's the only hint I can find. I'm wanting to get this running on my phone and, unfortunately, it happens to be an iphone6 Any ideas?

Hi Sarah, Since you have an iPhone 6, I'd try it on your actual phone. Simulators are good, but they're not as good as real hardware. You "should" I think be able to plug your phone into your Mac and Xcode should recognize it. Then just select run on device instead of using a simulator. Mark

With the i6 simulator the build works but fails to run. With my phone it fails to build. I'm working through the codesigning docs Ed has posted in the How To section as I feel like that might be the answer. Now, just to spite me, Apple have turned off the Certificate forms.

I've found some whack stuff going on. iPhone 6s works but now the rest don't. I've downloaded a clean project, saved it in a new location. Menu with Image is OK but webpages that open with 6s don't open with the simulator or my phone. 2016-03-15 12:05:32.181 nzpif2[1546:275283] -[NSDecimalNumber isEqualToString:]: unrecognized selector sent to instance 0x78fa36c0 Now to go and find out what it thinks it's looking for!

I turned off the screen that appeared to be jamming the app and still got errors referencing the screen. Some wise words from Smug came back to me about "Clean" not always being enough. Cleared derived data and did a simulator reset and I seem to be back on track. Older, greyer, and frazzled but on track :)

Yep! Sometimes that old junk hangs around no matter how hard you try to get rid of it. Smug's a wise man! Interesting that you're having issues on such a basic app. In all reality, it should "just work." Mark

Interesting is right. Awfully glad I'm having my learning curve on something like this and not something more complex.