Problem with autoloyaout in ios7?

Question

Objective-C

When trying to create a project with one UIViewController / UINavigationController, the following problem occurred:
If you specify a target from ios5 in the project and disable autoloyaout (because it works since ios6) in the interface builder, then an exception is thrown after launch:

-[NSKeyedUnarchiver decodeInt32ForKey:]: value for key (UIKeyAutomaticallyAdjustsScrollViewInsets) is not an integer number'

Did a search on the official apple developer forum.
I found similar questions, and two solutions to the problem that do not suit me.
1. Make two identical storyboards, one with autoloyaout enabled and the other disabled, and upload one for ios5, the other for ios 6-7.
2. Refuse support for ios5, and make a minimal target for ios6.
What do you think about this?
How will you solve this problem in your projects?
www.dropbox.com/s/txw2wwrqogs4tb1/MyUI.zip - Xcode 5 beta test project code
, sdk 7.0

Answer 1

Thanks everyone for the replies.
The problem is as expected LIAL in xcode 5.
It creates the wrong project.
If you create a project in xcode4 and then open it in xcode5, then everything is ok.
These are the crutches.

Answer 2

I don't think you should bother with iOS5.
According to statistics, the share of people sitting on iOS versions below 6.0 for iPhone is less than 6% ( Proof ) - so you can use autolayout. if all the same these 6% are important, then you can use the old and not very good struts & springs

Answer 3

If there is a loyal audience sitting on old devices, then it would be reasonable to ensure compatibility, even if you have to duplicate storyboards. For new projects - depends on the specifics of the project, the question is individual.

Answer 4

I think you can open the storyboard in a text editor, find entries there
and try to change YES/ NOto 1/0, since it expects a number there,
or completely remove this parameter

Answer 5

what demo are you looking at in ECSlidingViewController? Theoretically, TransitionFun should probably work, but BasicMenu should crash