Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

SDK 1.3 Breaking iPad backwards compatibility?

I'm developing an iPhone app, which compiled using iPhone SDK 3.1 was working in the iPad emulator prior to changing my application to the Titanium 1.3 SDK.

The basic error is as follows:

2010-05-20 16:35:06.165 MY PROJECT[32876:207] ERROR: unable to load AX Bundle: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.2.sdk/System/Library/AccessibilityBundles/MapKitFramework.axbundle

2010-05-20 16:35:06.338 MY PROJECT[32876:207] Failed to load NSMainNibFile MainWindow_ipad.

Can anyone advise….changing the Kitchen Sink to 1.3 has the same results. I can switch back to 1.2 and it is working again. I have also deployed to an iPad and it crashed with a black screen just like the emulator.

— asked May 20th 2010 by Mike Robinson
  • 1.3
  • backwards
  • compatibility
  • ipad
  • sdk

7 Answers

  • I've confirmed this problem and have created a bug report - as noted, 1.2.1 does not have this problem if the lack of iPad compatibility is a showstopper for you. Also, 1.3.0 iPhone apps are being approved, so iPad compatibility is likely not a hard requirement.

    — answered May 24th 2010 by Kevin Whinnery
    1 Comment
    • Is there a link to download 1.2.1? I just have 1.2.0 and 1.3.0

      — commented May 31st 2010 by Nick Haffie-Emslie
  • iPad compatibility is broken on 1.3 at the moment (at least for me). You'll need to roll back to 1.2.x to build an app which runs on iPad as well as iPhone et al (and I presume Apple are testing iPad compatibility, so 1.2.x would be advisable if you plan to submit to the store).

    — answered May 20th 2010 by Damien Elmes
  • I am encountering this same problem … Anyone know when this issue might be resolved?

    — answered May 21st 2010 by JD Hofer
  • Damn, I just ran into this too. :(

    EDIT: Had an app approved a day ago that was built with 1.3.0 and it went right through, so Apple is not currently testing for iPad compatibility.

    — answered May 24th 2010 by Dan Giulvezan
  • So if you get approved with a non-iPad-compatible app (built on 1.3.0), can people still sync it to their iPads? Sounds like a recipe for bad ratings, no?

    — answered May 31st 2010 by Nick Haffie-Emslie
  • Still really waiting for this, indeed. Maybe the Appcelerator guys can release a quick patch for this?

    — answered June 16th 2010 by Doney den Ouden
  • I just realized I had the same problem with an app that just went live.
    I have been able to fix it by removing the line NSMainNibFile~ipad: MainWindow_ipad from the info.plist (and, off course, recompiling and submitting the app. Sigh). Why would a seperatie nib file be needed? It's still an iPhone app, not an iPad one (and running in simulated mode).

    — answered July 3rd 2010 by Martijn Pannevis
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.