Strictly speaking, the above tips are not wrong constraints, but redundant constraints. For example, setting the top and bottom margins and pinning the height at the same time will cause such problems. It feels like your problem is that you set the height of UIView:0x166ea400 to 37, and then set it equal to 0.0894 of the width of another UIView:0x16526700. This is redundant. The troubleshooting method is to look for UIView one by one in the storyboard. 37 is a good entry point. This is what I did. It’s very stupid.
Suppose you set the height of a View to be equal to the width of another view1, and the width of view1 is equal to the width of view2. Then the width of view2 is not a certain value, which will cause conflicts. This should be a problem of setting the constraint priority?
Strictly speaking, the above tips are not wrong constraints, but redundant constraints. For example, setting the top and bottom margins and pinning the height at the same time will cause such problems. It feels like your problem is that you set the height of UIView:0x166ea400 to 37, and then set it equal to 0.0894 of the width of another UIView:0x16526700. This is redundant.
The troubleshooting method is to look for UIView one by one in the storyboard. 37 is a good entry point. This is what I did. It’s very stupid.
Suppose you set the height of a View to be equal to the width of another view1, and the width of view1 is equal to the width of view2. Then the width of view2 is not a certain value, which will cause conflicts. This should be a problem of setting the constraint priority?