I am trying to debug + understand the limitations of autodetection and notice that when debugging a view using xcode (using the cool layer), I noticed that on one element in the view, the constraints look like this:

and the view really ignores these limitations.
All restrictions have the same priority (1000), since I want them all. All restrictions were made using the interface constructor, not through code, and there are no warnings or conflicts in IB.
But at runtime I see this
Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
"<NSLayoutConstraint:0x79684f10 V:[UIImageView:0x79686800(>=160)]>",
"<NSLayoutConstraint:0x7968a310 V:[UIImageView:0x79686800]-(130.5)-| (Names: '|':UIView:0x79686790 )>",
"<NSLayoutConstraint:0x7968a340 V:|-(0)-[UIImageView:0x79686800] (Names: '|':UIView:0x79686790 )>",
"<NSLayoutConstraint:0x796997b0 'UIView-Encapsulated-Layout-Height' V:[CoverCell:0x79686570(192)]>",
"<NSAutoresizingMaskLayoutConstraint:0x7969cd30 h=-&- v=-&- UIView:0x79686790.height == CoverCell:0x79686570.height>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x79684f10 V:[UIImageView:0x79686800(>=160)]>
So, I understand that some rules conflict, but I'm not sure how to read this
>=160 UIImageView, 160, 130,5 - ( systemLayoutSizeFittingSize:UILayoutFittingCompressedSize 0. , 160 + 130,5)
, .
, IB?