当使用UITableViewAutomaticDimension并在单元格内的视图上更改高度约束时，我有这个错误。

我最终发现这是由于约束常数值没有四舍五入到最近的整数。

let neededHeight = width / ratio // This is a CGFloat like 133.2353
constraintPictureHeight.constant = neededHeight // Causes constraint error
constraintPictureHeight.constant = ceil(neededHeight) // All good!

调整文本视图以适应其内容，并将高度约束常数更新为结果高度，为我固定了uiview - encapsulation - layout - height约束冲突，例如:

[self.textView sizeToFit];
self.textViewHeightConstraint.constant = self.textView.frame.size.height;

另一种可能性:

如果你使用auto layout来计算单元格高度(contentView的高度，大多数时候如下所示)，如果你有uitableview分隔符，你需要添加分隔符高度，以便返回单元格高度。一旦你得到正确的高度，你就不会有自动布局警告。

- (CGFloat)calculateHeightForConfiguredSizingCell:(UITableViewCell *)sizingCell {
   [sizingCell setNeedsLayout];
   [sizingCell layoutIfNeeded];
   CGSize size = [sizingCell.contentView systemLayoutSizeFittingSize:UILayoutFittingCompressedSize];
   return size.height; // should + 1 here if my uitableviewseparatorstyle is not none

}

我能够解决这个错误通过删除一个假cell.layoutIfNeeded()，我在我的tableView的cellForRowAt方法。

No one answered it how to solve the case in storyboard. You have the case of mine, top bottom constraint with fixed height with priority 1000. That is why, when first time loading , as the table view cell height is 0, tries to set the element with the fixed height, causing a constraint conflict. (I am trying to insert 40 pixel in a 0 pixel height area, so compiler tries discarding the 40 pixel height). Once the tableview loaded, it will not generate (Like pop back to the tableview or switching tab bar tab)

所以将优先级从必需的@1000更改为高@750或低@250。第一次加载时，不考虑低优先级，然后在layoutSubviews()中调整所有约束的大小

99.9%的情况下，当使用自定义单元格或标头时，UITableViews的所有冲突都发生在表第一次加载时。一旦加载，你通常不会再看到冲突。

This happens because most developers typically use a fixed height or anchor constraint of some sort to layout an element in the cell/header. The conflict occurs because when the UITableView first loads/being laid out, it sets the height of its cells to 0. This obviously conflicts with your own constraints. To solve this, simply set any fixed height constraints to a lower priority (.defaultHigh). Read carefully the console message and see which constraint the layout system decided to break. Usually this is the one that needs its priority changed. You can change the priority like this:

let companyNameTopConstraint = companyNameLabel.topAnchor.constraint(equalTo: companyImageView.bottomAnchor, constant: 15)
    companyNameTopConstraint.priority = .defaultHigh

NSLayoutConstraint.activate([
            companyNameTopConstraint,
           the rest of your constraints here
            ])