9

Since I've updated to Xcode 7.3 I have a problem with UIStackView. If I create an empty project and just put two UILabels in UIStackView with default hugging and compression priorities, it shows me AutoLayout misplacement error. It even doesn't work with one(!) UILabel in UIStackView, so priorities doesn't matter (as I think, maybe there is the problem).

As I remember in Xcode prior 7.3 everything was fine. I checked on two MacBook Pro separately, it's the same issue.

Does anybody know how to fix it?

enter image description here enter image description here

egor.zhdan
  • 4,555
  • 6
  • 39
  • 53
Evgeny
  • 631
  • 6
  • 17

3 Answers3

9

enter image description here This is a bug appears in Xcode 7.3, so you can ignore it as what he said matt.

The problem

The storyboard can not calculate the intrinsic content size of subviews when you use UIStackView

Solution

If you hate seeing warnings in your storyboard you can fixe it like below :

You should do these steps for each subview of your UIStackView

  • Tap the warning of your subview
  • Tap "Update frames" option
  • Choose "Placeholder" of the subview intrinsic size in the fourth menu in the inspector view

Like that you will not see warnings, and you can see if any ambiguities exist

The disadvantage is you should do this steps each time you change your subview (example: changing the size of text of an UILabel)

Hoping that Apple fixes this bug in the next release

HamzaGhazouani
  • 6,464
  • 6
  • 33
  • 40
4

Ignore the warnings. The storyboard has never quite understood stack views. The constraints will be correct at runtime and that's all that matters.

matt
  • 515,959
  • 87
  • 875
  • 1,141
  • Yes, in runtime it works, but also was working until 7.3 in Interface Builder. Does Apple know the issue and do they plan to fix it? :( – Evgeny Apr 02 '16 at 13:07
  • Do you have the bug number? - So I can report it too as a duplicate :) – nacho4d Apr 09 '16 at 13:13
  • @matt how can I be sure the constrains are good are runtime? Is there a way I can check ambiguosity at runtime? – nacho4d Apr 09 '16 at 13:18
3

I have a different trick for eliminating the warnings and making 'update frames' work properly.

Advantage:

Doesn't require changing placeholder values every time text changes

Disadvantage:

Extra views that are unnecessary when Xcode 8 comes out

Steps:

  • Embed each UILabel inside a UIView.
  • Constrain the UIView to size itself based on the label (match leading, trailing, bottom, and top)

It seems like UIStackView (in Xcode 7) can't understand the intrinsic content size of a label, but CAN understand the intrinsic content size of a view - so put the label in a view and presto!

enter image description here

charmingToad
  • 1,597
  • 11
  • 18