HomeiDevBlogADayAre Your (Older) Apps Ready for iOS6?


Are Your (Older) Apps Ready for iOS6? — 17 Comments

  1. Have you tested those same apps on iOS 6 but using the App Store version instead? Anytime you build with a newer SDK, you are agreeing to the new terms of the API — but if you built against an older version, it is up to Apple to maintain backwards compatibility (assuming that the original program followed the original terms, that is).

    I wouldn’t want to discourage anyone from updating their apps to newer versions using the latest SDKs, but at the same time, a new iOS release shouldn’t require new builds of all the apps. If an older app that worked fine under iOS 5.1 stops working under 6.0, a bug should be filed against iOS 6.

  2. Hi Dennis. No, I have not tried the app store versions of my older apps on a device running iOS6 yet, but that’s a good suggestion. While I would tend to agree with your thought about backward compatibility of apps built against older SDKs under newer iOS versions, I am cynical, and think it better to be safe than sorry. 🙂 Plus, it never hurts to update your app and let your users know that it works on the latest and greatest SDK.

  3. I had the same problem with auto rotation if I didn’t set the rootViewController. My App Store app worked fine but when I rebuilt with iOS 6 it did not.

  4. Great post. Thanks for the heads up on this. I tried a couple of our older apps (Euchre HD and Picross HD) and sure enough they both had the same problem. I’m still trying to figure out the right way to fix it. I’m also having some assert issues with GameCenter login via landscape mode right now.

  5. I’m having the same problem. I installed xcode 4.5 this afternoon and now my app is having issues. But the above solution does not work for me.

  6. Thanks Hawk, I’m new to app development. Was going crazy trying to figure out why my perfectly working (on previous xcode) landscape app would not fit the screen or rotate in the update. What a find to stumble onto your tip! Disappointed that Apple did not email me of this problem and fix. I know their must be dozens of developers out there pulling their hair out. BTW it might help to put in that the fix goes into AppDelegate.m, for us less experienced to Xcode. Also is this an IOS problem or the new Xcode problem?

  7. Hi
    I was having the same problem. Another solution where you don’t have to type any code is to just go to
    – MainWindow.xib (or whatever it’s called)
    – Click Window
    – Connect rootViewController to the UIViewController you want to use as default

  8. You’ve saved my sanity, thank you! All of a sudden my iPad apps started doing it after upgrading and rebuilding (iOS6). I was going crazy. You should post it to stackoverflow and get full credit!

  9. Thanks. I just found this doing a google search and was able to fix my iOS6 problem. Really appreciate people like you taking time to write this down. How did you figure out this was the way to solve it?

  10. Glad the post helped you out. I compared the code in question (which was quite old, circa iPhone OS 3) to current templates. Plus, the error was fairly explicit and gave a good clue.

  11. Thanks so much for the info, you saved me a headache! I used the tip about connecting the rootviewcontroller to the main nib. This quickly solved my error. It might be worth updating your post to include that solution, since it was so easy. Again, thanks so much!

  12. This one actually works. There are so many ppl asking the same questions and none of the solutions online works for me. But, this one nailed it for me.
    Many thx.

Leave a Reply

Your email address will not be published. Required fields are marked *

HTML tags allowed in your comment: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>