Finding cause of “Automatic Preferred Max Layout W

Question

I know the reason of this warning and how to solve it: to give a preffered width to the label.

The problem is that, when I click that warning, I don't see any label/view/viewcontroller selected. The storyboard opens and that's it. There are many view controllers with many views in my storyboard. How can I find out which label is causing the problem without iterating through all the view controllers manually? When I click the warning, I expect it to take me to the view causing the warning, but it just opens the storyboard.

Answer 1

As said in that post, you can also use this regex <label(?!.*preferredMaxLayoutWidth) in storyboard source to find all labels that do not have a preferredMaxLayoutWidth setted. Then correct it.

Answer 2

Is that the warning from a collection view? If so I'd guess it's a cell and a label with number of lines set to zero.

Answer 3

just remove number of line from label and set it programmatically

[label setNumberOfLines:2];

Answer 4

I had the same problem in an existing project developed in 7.1 without autolayouts. Once I migrated the app to iOS8 and changed in the project file the version to 8.0, for some reason I got that warning in the Xib's where I used UILabel's with multiple lines.

in order to correct the problem, select the file inspector for the Xib and check the version it Builds for, in my case it was still for iOS7

you should change the Build for to the relevant version

and the warning will disappear as it did in my case :-)

Answer 5

Here is one way to find the specific label that is causing this warning:

1. Right click on the warning and choose "Reveal in Log"
2. The warning in the log will be highlighted. Copy the interface builder object ID for this label (it looks like xxx-xx-xxx).
3. Paste this in the Find Navigator. When you click on this result it will open the interface builder with the offending label selected.

Answer 6

Answer of @Don Eichenseer is great. But for those who want to solve it: I've got the same problem before. The issue was because of a UILabel which its Lines property (in Attributes inspector) was more than 1. When you have found the related UILabel, set it Lines to 1.