iOS 8 / XCode 6 autolayout constraints applied after view appears
I have a project that was working just fine with XCode 5 and iOS 7, but when I recently downloaded XCode 6, I noticed some weird behavior with autolayout.
I have a storyboard with a view that just has a UIImageView and two UILabels. This view gets loaded using a UiPageViewController. The UIImageView is centered horizontally and vertically in the view and there are constraints specifying the distance of the two labels from the image view. When there is a case when the storyboard and autolayout values conflict (for example, in the storyboard, one label is 20 pixels above the image view but the autolayout says it should be 40 pixels above), it used to be that the autolayout value was successfully applied before the view loaded. Thus, when the view gets shown for the first time, everything is in the right place.
Now with iOS 8 / XCode 6, I’m seeing that the view loads and then things jump to their final autolayout position. This jump is noticeable to the end user both in the simulator and on a real device, and it’s really annoying. Is there a way to go back to the old behavior? As far as I’m aware, no code has changed to cause this issue.
- iOS Autolayout: Issue with UILabels in a resizing parent view
- How to use auto-layout to move other views when a view is hidden?
- Setting mask layer on UITableViewCell's subview overrides Auto Layout constraints
- iOS change auto layout constraints when device rotates
- UIScrollView + Centered View + Ambigous Scrollable Content Size + many iPhone sizes
- How to turn on/off auto layout for a single view controller in storyboard
3 Solutions Collect From Internet About “iOS 8 / XCode 6 autolayout constraints applied after view appears”
Where is your code that is making changes to your constraints?
If you’re keeping it in viewWillAppear: you will have that problem. I found that viewDidLayoutSubviews works well for iOS8 but not always for iOS7 backwards.
Eventually, if you cant use viewDidLayoutSubviews, what I’d suggest is hide the container view in viewDidLoad and unhide it in viewWillAppear, only after the constraints have been applied. It gets you a small extra delay when loading the screen but the constraints change gets transparent to the user.
I had a similar issue and put items into a container view in preparation for hiding and then showing them as suggested in the other answer.
I didn’t love that as a solution and ended up not having to do it.
Simply putting them in a container view that was pegged to the controller’s view stopped the issue from happening.
For me it was an issue with the tab bar in my project. I didn’t need it in that view and I hid it on push. So when the view got pushed onto the stack the bar was hidden and the constraints adjusted accordingly. So I just put the tab bar back in.
- How to programmatically turn ViewController into a UITableViewController
- Swift 2.0 Get Mirrored Superclass Properties
- Synthesize error “Missing Context for Property Implementation Declaration”
- Swift: How to Open local pdf from my app to iBooks
- ViewController Segue Xamarin
- iOS in-app purchase auto-renewable subscriptions free trial option not available?
- how to change orientation for AVCaptureMovieFileOutput in swift
- How to auto increment the build number in Xcode 5
- convert UIImage to NSData and back to UIImage
- No restore button for in app purchase causes rejection
- Swift 'NSArray?' does not have member named 'count'
- How to fill background image of an UIView
- Swift – Compressing video files
- Using UIAppearance to change label height
- NSURLConnection Authorization Header not Working