blocks|key|4701|text|在手动添加代码中的约束时，我遇到了同样的问题。在代码中，我执行了以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4702|{
++++[self+setTranslatesAutoresizingMaskIntoConstraints:YES];
++++[self+addSubview:someView];
++++[self+addSubview:someOtherView];
++++[self+addConstraint:...];
}|code-block|syntax|javascript|4703|假说|offset|length|style|BOLD|4704|据我所知，问题是当您禁用translatesAutoresizingMaskIntoConstraints时，UITableViewCell开始使用自动布局，并自然失败，因为layoutSublayersForLayer的底层实现没有调用超级。有Hopper或其他工具的人可以证实这一点。既然你在使用IB，你可能想知道为什么这是个问题.这是因为使用IB会自动禁用对其添加约束的视图的translatesAutoresizingMaskIntoConstraints+(它将自动添加一个宽度和高度约束)。|CODE|4705|溶液|4706|我的解决方案是把所有东西都转移到contentView。|4707|{
+++[self.contentView+addSubview:someView];
+++[self.contentView+addSubview:someOtherView];
+++[self.contentView+addConstraint:...];
}|4708|我不能100%25确定这在Interface中是否有效，但是如果您将所有东西从单元格中推开(假设您有直接在其上的东西)，那么它应该可以工作。希望这对你有帮助！|4709|entityMap^0|0|0|0|2|0|C|15|2F|N|5B|15|0|0|2|0|G|B|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@$I|12|J|13|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@$I|15|J|16|K|O]|$I|17|J|18|K|O]|$I|19|J|1A|K|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@$I|1C|J|1D|K|L]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1E|8|@$I|1F|J|1G|K|O]]|9|@]|A|$]]|$1|T|3|U|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|V|3|W|5|6|7|1I|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Y|$]]

I encountered the same problem while manually adding constraints in code. In code, I was doing the following:

<pre><code>{
 [self setTranslatesAutoresizingMaskIntoConstraints:YES];
 [self addSubview:someView];
 [self addSubview:someOtherView];
 [self addConstraint:...];
}
</code></pre>

Hypothesis

From what I can tell, the issue is that when you disable <code>translatesAutoresizingMaskIntoConstraints</code>, UITableViewCell starts to use Auto Layout and naturally fails because the underlying implementation of <code>layoutSublayersForLayer</code> does not call super. Someone with Hopper or some other tool can confirm this. Since you're using IB you're probably wondering why this is an issue... and that's because using IB automatically disables <code>translatesAutoresizingMaskIntoConstraints</code> for views that it adds constraints to (it will automatically add a width and height constraint in their place).

Solution

My solution was to move everything to the <code>contentView</code>.

<pre><code>{
 [self.contentView addSubview:someView];
 [self.contentView addSubview:someOtherView];
 [self.contentView addConstraint:...];
}
</code></pre>

I'm not 100% sure if this will work in Interface Builder, but if you push everything off of your cell (assuming that you have something directly on it) then it should work. Hope this helps you!

blocks|key|3901738|text|我也经历过同样的事情。结果是，如果您以编程方式从ShopCell+.+.xib/storyboard中添加了一个子视图，该视图使用自动布局作为另一个视图的子视图，则可能会抛出该异常，这取决于您的约束配置方式。我的猜测是，在IB中创建的约束是在以编程方式将视图添加为子视图时造成的麻烦，因为它随后是维护来自viewA+-->+viewB的约束，同时您可以添加viewB作为viewC的子视图。你明白了(那句话连我自己都不明白)？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3901739|在我的情况下--因为引起问题的是非常简单的视图--我是通过编程而不是在IB中创建视图的。解决了这个问题。您可以将这些视图提取到其他xib文件中，并禁用这些文件的自动布局。我想那会管用的。|3901740|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have been experiencing the same thing. It turned out that if you programmatically add a subview from your ShopCell .xib/storyboard, that uses auto layout, as a subview to another view, that exception might be thrown, depending on how your constraints are configured. My guess is that the constraints created in IB is what creates the troubles when programmatically adding a view as a subview, since it's then maintaing constraints from viewA --> viewB meanwhile you might add viewB as a subview of viewC. You got it (that sentence is even confusing myself)?

In my situation - since it was very simple views that caused the problem - I created the views programmatically and not in IB. That solved it. You might extract those views to other xib files and disable auto layout for those. I guess that'd work.

blocks|key|3901768|text|显然，UITableViewCell的layoutSubviews实现没有调用super，这是自动布局的一个问题。我想看看是否把下面的类别放到项目中去解决问题。它帮助了一个测试项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3901769|#import+<objc/runtime.h>
#import+<objc/message.h>

@implementation+UITableViewCell+(FixUITableViewCellAutolayoutIHope)

%2B+(void)load
{
++++Method+existing+=+class_getInstanceMethod(self,+@selector(layoutSubviews));
++++Method+new+=+class_getInstanceMethod(self,+@selector(_autolayout_replacementLayoutSubviews));

++++method_exchangeImplementations(existing,+new);
}

-+(void)_autolayout_replacementLayoutSubviews
{
++++[super+layoutSubviews];
++++[self+_autolayout_replacementLayoutSubviews];+//+not+recursive+due+to+method+swizzling
++++[super+layoutSubviews];
}

@end|code-block|syntax|javascript|3901770|我可能会添加在表单元格上使用backgroundView时出现的问题，因为它会作为子视图添加到单元格中(而大多数子视图应该添加到表单元格的contentView中，这通常会更好地工作)。|3901771|注意：这个bug似乎是在iOS7中修复的；我删除了这段代码，或者至少添加了一个运行时检查，这样只有在iOS6上运行时才能完成。|offset|length|style|BOLD|3901772|entityMap^0|0|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Apparently, UITableViewCell's layoutSubviews implementation does not call super, which is a problem with auto layout. I'd be interested to see if dropping the below category into projects fixes things. It helped in a test project.

<pre><code>#import &lt;objc/runtime.h&gt;
#import &lt;objc/message.h&gt;

@implementation UITableViewCell (FixUITableViewCellAutolayoutIHope)

+ (void)load
{
 Method existing = class_getInstanceMethod(self, @selector(layoutSubviews));
 Method new = class_getInstanceMethod(self, @selector(_autolayout_replacementLayoutSubviews));

 method_exchangeImplementations(existing, new);
}

- (void)_autolayout_replacementLayoutSubviews
{
 [super layoutSubviews];
 [self _autolayout_replacementLayoutSubviews]; // not recursive due to method swizzling
 [super layoutSubviews];
}

@end
</code></pre>

I might add the problem showed up for me when using a backgroundView on the table cell, as that gets added as a subview to the cell (whereas most subviews should be added to the table cell's contentView, which should usually work better).

Note: It appears this bug is fixed in iOS7; I was able to remove this code, or at least add a runtime check so that it's only done if running on iOS6.

blocks|key|3880436|text|我通过为我的自定义表视图单元格的所有子视图关闭"Autolayout“来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3880437|在自定义单元格的xib中，选择一个子视图并取消选中“文件检查器”>“接口生成器文档”>“使用自动退出”|3880438|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I resolved the issue by turning off "Autolayout" for all the subviews of my custom Table View Cell.

In the xib for a custom cell, select a subview and uncheck File Inspector > Interface Builder Document > Use Autolayout

blocks|key|3901843|text|我遇到这个问题是因为我最初向xib文件中添加了一个UIView而不是一个UITableViewCell。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3901844|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I encountered this one because I had initially added a UIView instead of a UITableViewCell to a xib file.

blocks|key|3880458|text|几个月来我都有同样的毛病。但我发现了问题所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3880459|创建IB文件时，已经添加了一个UIView。如果使用此视图，当禁用自动布局时，应用程序不会崩溃(但还有其他问题)。使用自动布局时，必须在Object：：UITableViewCell中选择右视图。|offset|length|style|CODE|BOLD|3880460|实际上，您应该始终使用，因为所有子视图都被添加到UITableViewCell的contentView中。|3880461|就这样。一切都会好的。|3880462|entityMap^0|0|F|6|24|F|23|J|0|O|F|14|B|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]|$D|U|E|V|F|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@$D|X|E|Y|F|G]|$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|N|$]]

I had the same bug for few months. But I found what was the problem.

When I create an IB file, a <code>UIView</code> is already added. If you use this view, the app doesn't crash when auto layout is disabled (but there are other issues). When you use auto layout, you have to select the right view in the Object Library : <code>UITableViewCell</code>.

In fact, you should always use this item because all subviews are added to the <code>contentView</code> of the <code>UITableViewCell</code>.

That's all. All will be fine.

blocks|key|3880483|text|我遇到了这种情况，它似乎与UITableViewCell子类相关，因为原型单元格中特别添加了其他自定义的UIView子类。我在这里强调“自定义”，因为我已经成功地处理了只有UIKit子的单元格，但是当我试图为我创建的定制视图构建约束时，它就失败了，抛出了作者问题中所述的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3880484|我不得不将我的细胞分割成不使用AutoLayout的独立的nibs。|3880485|希望苹果公司能把这一烂摊子清理干净。|3880486|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I am encountering this and it seems that it is related to UITableViewCell subclasses as prototype cells that specifically have other custom UIView subclasses added to them. I stress the 'custom' here because I have been successful with cells that just have UIKit children, but it falls over when trying to build the constraints for views I have created bespoke, throwing the error stated in the authors question.

I have had to separate my cells into independent nibs that don't use AutoLayout.

Let's hope Apple clean up this mess.

blocks|key|3901935|text|通过将backgroundView连接器从我的背景UIImageView和accessoryView连接器从UIButton自定义中解除耦合，消除了这个错误。我怀疑这些不是我想要用的方式。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3901936|entityMap^0|3|E|P|B|11|D|1I|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I eliminated this error by uncoupling the <code>backgroundView</code> connector from my background <code>UIImageView</code> and <code>accessoryView</code> connector from my <code>UIButton</code> customisations. I suspect that these were not meant to be used the way I was using them.

blocks|key|4821|text|我也有过同样的问题。问题在于我创建细胞Xib的方式。我创建了一个类似于普通的Xib，并将默认的"UIView“类型更改为我的自定义UITableViewCell类。正确的方法是首先删除默认视图，然后将表视图单元对象拖到xib上。这里有更多详细信息：http://allplayers.github.io/blog/2012/11/18/Custom-UITableViewCell-With-NIB/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4822|entityMap|0|LINK|mutability|MUTABLE|url|http://allplayers.github.io/blog/2012/11/18/Custom-UITableViewCell-With-NIB/^0|3G|24|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had the same issue. The problem was in the way I was creating the cell Xib. I created a Xib like normal and just changed the type of the default "UIView" to my custom UITableViewCell class. The correct way to is to first delete the default view and then drag the table view cell object onto the xib. More details here : <a href="http://allplayers.github.io/blog/2012/11/18/Custom-UITableViewCell-With-NIB/" rel="noreferrer">http://allplayers.github.io/blog/2012/11/18/Custom-UITableViewCell-With-NIB/</a>

blocks|key|5133|text|我今天第一次遇到这个问题。到目前为止，我在使用prototype+UITableViewCell子类方面有一些不同的经验，但从未遇到过这个问题。我所使用的细胞的不同之处在于，我有一个IBOutlet到-backgroundView，我用它来给细胞着色。我发现，如果我创建了一个新的属性，并且仍然添加了一个扩展整个单元的新的UIView，那么这个断言就消失了。为了验证这是原因，我回到了将此视图附加到backgroundView出口并重新出现断言。到目前为止，在子类原型AutoLayout中使用UITableViewCell还没有其他问题，因为我已经做了这个更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5134|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had run into this issue first time today. Up until now I had some various experience in using prototype UITableViewCell subclasses but never ran into this issue. What was different about the cell I was working with was that I had an IBOutlet to the -backgroundView which I was using to color the cell. I found that if I created a new property and still added a fresh UIView which stretched the span of the entire cell, this assertion went away. To verify this was the cause, I went back to attaching this view to the backgroundView outlet and the assertion reappeared. So far, no other issues using AutoLayout in a subclassed prototype UITableViewCell since I've made this change.

blocks|key|3880547|text|将子视图添加到单元格的contentView中，而不是单元格本身。因此，与其：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3880548|[self+addSubview:someView];|offset|length|style|CODE|3880549|你必须用|3880550|[self.contentView+addSubview:someView];|3880551|entityMap^0|0|0|R|0|0|0|13|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

Add your subviews to the contentView of the cell instead of the cell itself.
So instead of:

<code>[self addSubview:someView];</code>

you must use

<code>[self.contentView addSubview:someView];</code>

blocks|key|5151|text|我看到这是修改layoutSubviews实现中的约束的结果。将调用从开始到结束的调用的方法解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5152|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was seeing this as a result of modifying constraints in my implementation of layoutSubviews. Moving the call to super from the beginning to the end of the method fixed the problem.

blocks|key|5154|text|在某些情况下，这很容易解决布局问题(取决于布局)。在您的UITableView子类中，在awakeFromNib或init中设置自动调整大小掩码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5155|self.contentView.autoresizingMask+=+UIViewAutoresizingFlexibleWidth+%7C+UIViewAutoresizingFlexibleHeight;|code-block|syntax|javascript|5156|通过defaut将其设置为UIViewAutoresizingNone|5157|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In some situations, this solves the layout problem easily (depending on your layout). Inside you UITableView subclass, in either awakeFromNib or init, set the autoresizing mask:

<pre><code>self.contentView.autoresizingMask = UIViewAutoresizingFlexibleWidth | UIViewAutoresizingFlexibleHeight;
</code></pre>

By defaut it is set to UIViewAutoresizingNone

blocks|key|3880623|text|就我而言，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3880624|为UITableView的自动布局而引用的UITableView被分配给UITableView的backgroundView。|3880625|self.tableView.backgroundView+=+self.tableBackgroundImageView;|code-block|syntax|javascript|3880626|因此，我从UIImageView+(根视图)中删除了backgroundView的UIView，并重置(删除)了对该UIImageView的所有自动布局引用。我将UIImageView放在UIView(根视图)的外部作为背景。然后在代码中分配给backgroundView的UITableView。|3880627|然后修好。|3880628|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case,

The referenced UIImageView for the auto layout for UITableView is assigned to backgroundView of the UITableView.

<pre><code>self.tableView.backgroundView = self.tableBackgroundImageView;
</code></pre>

So, I removed UIImageView for backgroundView from the UIView(Root view) and reset(remove) all auto layout reference to that UIImageView. I placed that UIImageView for background at the outside from the UIView(root view). And then assign to the backgroundView of the UITableView in code.

Then fixed.

blocks|key|5173|text|我也遇到了同样的问题，从UIView变成UITableViewCell解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5174|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem , changing from UIView to UITableViewCell solved the problem.

blocks|key|3902123|text|如前所述，当您创建用于UITableView的视图时，必须删除默认创建的视图，并将UITableViewCell或UITableViewHeaderFooterView拖动为根视图。但是，有一种方法可以修复XIB，以防您错过了该部分。例如，您必须在文本编辑器和根标记中打开XIB文件，并直接将属性translatesAutoresizingMaskIntoConstraints添加/更改为YES。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3902124|<view+contentMode="scaleToFill"+horizontalHuggingPriority="1000"+id="1"+translatesAutoresizingMaskIntoConstraints="YES"+customClass="MXWCollapsibleTableHeaderView">|3902125|entityMap^0|3C|27|44|15|5F|3|0|0|4K|0|4K|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|D]|$9|P|A|Q|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|D]]|E|@]|F|$]]|$1|I|3|-4|5|6|7|W|8|@]|E|@]|F|$]]]|J|$]]

As someone above has already stated, when you create a view for use in a UITableView, you have to delete the view created by default and drag a UITableViewCell or UITableViewHeaderFooterView as the root view. However, there is a way to fix the XIB in case you had missed that part. You have to open the XIB file in a text editor and in the root tag and its direct child add/change the attribute <code>translatesAutoresizingMaskIntoConstraints</code> to <code>YES</code>, for example 

<code>&lt;view contentMode="scaleToFill" horizontalHuggingPriority="1000" id="1" translatesAutoresizingMaskIntoConstraints="YES" customClass="MXWCollapsibleTableHeaderView"&gt;</code>

blocks|key|3902148|text|我已经找到了解决办法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3902149|在我的例子中，我在情节提要中创建了单元格视图(启用了自动布局)，并且在ViewController.m中定义了自定义的UITableViewCell接口，我必须将接口移动到ViewController.h。|3902150|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have found the solution.

In my case, I created cell's view in storyboard (with auto layout enabled) and I defined the custom UITableViewCell interface in my ViewController.m, I have to move interface to ViewController.h.

blocks|key|5218|text|当我使用故事板创建自定义UITableViewCell时，也遇到了同样的问题。幸运的是，我发现了这个问题，因为我将accessoryView(UITableViewCell+setAccessoryView:)释放到了添加到单元格中的UIButton。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5219|因此，当在iOS6上运行时，它发生在我的项目中。
|blockquote|5220|5221|溶液|offset|length|style|BOLD|5222|我释放accessoryView和我的按钮之间的出口，其中包含自定义单元格。
|5223|5224|提案|5225|您不应该使用UITableViewCell的本机元素并对其进行更改。|5226|5227|entityMap^0|0|0|0|0|2|0|0|0|0|2|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|L|3|M|5|D|7|11|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|13|8|@$H|14|I|15|J|K]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|16|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|U|$]]

I encountered the same problem when I use the storyboard to create the custom UITableViewCell. Fortunately I found the problem, because I outlet the accessoryView([UITableViewCell setAccessoryView:]) to UIButton which I added to the cell. 

<blockquote>
 So it occurred in my project when run on the iOS6.
</blockquote>

Solution

<blockquote>
 I release the outlet between accessoryView and my button which
 contained the custom cell.
</blockquote>

Proposal

<blockquote>
 You shouldn't used the UITableViewCell's native elements and change
 it.
</blockquote>

blocks|key|5240|text|对于这个问题，我没有得到任何适当的解决方案，但是您可以通过使用框架而不将translatesAutoresizingMaskIntoConstraints属性设置为No来修复它(默认情况下是的，所以不要设置它)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5241|CGRect+headerViewFrame+=+CGRectMake(0,0,320,60);+//Frame+for+your+header/footer+view
UIView+*tableHeaderView+=+[[UIView+alloc]+initWithFrame:headerViewFrame];
tableHeaderView.translatesAutoresizingMaskIntoConstraints+=+Yes;+//Or+don't+set+it+at+all
[self.tableView+setTableHeaderView:tableHeaderView];|code-block|syntax|javascript|5242|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I didn't get any proper solution for this issue but you can fix it by using frames and not setting translatesAutoresizingMaskIntoConstraints property to No (by default its yes, so don't set it)

<pre><code>CGRect headerViewFrame = CGRectMake(0,0,320,60); //Frame for your header/footer view
UIView *tableHeaderView = [[UIView alloc] initWithFrame:headerViewFrame];
tableHeaderView.translatesAutoresizingMaskIntoConstraints = Yes; //Or don't set it at all
[self.tableView setTableHeaderView:tableHeaderView];
</code></pre>

blocks|key|4981|text|这个问题可能是由于忘记在viewDidAppear中调用viewDidAppear而引起的，但我相信这并不是唯一的原因。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4982|entityMap^0|C|D|S|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

This problem can be caused by forgetting to call <code>[super viewDidAppear:]</code> within <code>viewDidAppear</code>, but I'm sure it's not the only cause.

blocks|key|3880891|text|我在Xcode+6+(+iOS+7%2B+)中设置的表页脚视图也有类似的问题。解决方案采用nib文件的格式。显然，它被卡在Xcode+4格式或其他什么。将文件设置更改为"opens+in:+Xcode+6.0“(或默认设置)，立即修复它。偶然找到了解决方案:它让我抓狂，所以我删除了整个文件，并再次创建，显然是使用默认设置。我不知道为什么简单地用最新的Xcode编辑文件没有像通常那样将它转换成Xcode+5%2B格式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3880892|​|3880893|📷|atomic|offset|length|3880894|3880895|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3641bdb314eaa2d4d29534e73b2ba4da.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I had a very similar problem with a table footer view I was setting in Xcode 6, iOS 7+.
The solution was in the format of the nib file. Apparently it was stuck in Xcode 4 format or something.
Changing the file settings to "opens in: Xcode 6.0" (or Default, for that matter), instantly fixed it.
Found the solution by chance: it was driving me crazy, so I deleted the entire file and created again, obviously with the default settings. I have no idea why simply editing the file in the latest Xcode didn't convert it to a Xcode 5+ format, as it usually happens.

<img src="https://i.stack.imgur.com/uYXtt.png" alt="f">

blocks|key|5023|text|iOS+7中也出现了同样的问题(iOS+8似乎修复了)。对于我来说，解决方案是在我的[self.view+layoutIfNeeded]方法的末尾调用viewDidLayoutSubviews。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5024|entityMap^0|16|Q|23|L|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Had the same problem in iOS 7 (iOS 8 seems to fix). The solution for me was to call <code>[self.view layoutIfNeeded]</code> at the end of my <code>viewDidLayoutSubviews</code> method.

blocks|key|3902339|text|我没有在UITableViewCell上遇到类似的问题，而是在UITableView本身上遇到类似的问题。因为这是谷歌的第一个结果，所以我会在这里发布。事实证明，viewForHeaderInSection是问题所在。我创建了一个UITableViewHeaderFooterView并将translatesAutoresizingMaskIntoConstraints设置为NO。现在，有趣的部分来了：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3902340|iOS+7:|BOLD|3902341|//+don't+do+this+on+iOS+7
sectionHeader.translatesAutoresizingMaskIntoConstraints+=+NO;|code-block|syntax|javascript|3902342|如果我这样做，应用程序就会崩溃。|3902343|执行-layoutSubviews后仍然需要自动布局。UITableView的-layoutSubviews实现需要调用超级。
|blockquote|3902344|3902345|好的，我认为您不能在表视图头上使用自动布局，而只能在子视图上使用。但这并不是你以后看到的全部事实。总结:不要为iOS+7上的标题禁用自动调整大小的掩码。，否则它会正常工作。|3902346|iOS+8:|3902347|//+you+have+to+do+this,+otherwise+you+get+an+auto+layout+error
sectionHeader.translatesAutoresizingMaskIntoConstraints+=+NO;|3902348|如果我不使用它，我将得到以下输出：|3902349|不能同时满足约束。
|3902350|3902351|For+iOS+8您必须禁用标题的自动调整掩码。|3902352|不知道为什么会出现这种情况，但苹果似乎确实修复了iOS+8中的某些功能，而iOS+7和iOS+8的自动布局工作方式也有所不同。|3902353|entityMap^0|4|F|V|B|29|M|37|R|40|15|58|2|0|0|6|0|0|0|0|0|1D|R|0|0|6|0|0|0|0|0|0|O|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1N|8|@$9|1O|A|1P|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1Q|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1R|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|1S|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1U|8|@$9|1V|A|1W|B|H]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1X|8|@$9|1Y|A|1Z|B|H]]|D|@]|E|$]]|$1|X|3|Y|5|K|7|20|8|@]|D|@]|E|$L|M]]|$1|Z|3|10|5|6|7|21|8|@]|D|@]|E|$]]|$1|11|3|12|5|R|7|22|8|@]|D|@]|E|$]]|$1|13|3|-4|5|6|7|23|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|24|8|@$9|25|A|26|B|H]]|D|@]|E|$]]|$1|16|3|17|5|6|7|27|8|@]|D|@]|E|$]]|$1|18|3|-4|5|6|7|28|8|@]|D|@]|E|$]]]|19|$]]

I had a similar problem not on <code>UITableViewCell</code> but rather on <code>UITableView</code> itself. Because it is the first result in Google I'll post it here. It turned out that <code>viewForHeaderInSection</code> was the problem. I created a <code>UITableViewHeaderFooterView</code> and set <code>translatesAutoresizingMaskIntoConstraints</code> to <code>NO</code>. Now here comes the interesting part:

iOS 7:

<pre><code>// don't do this on iOS 7
sectionHeader.translatesAutoresizingMaskIntoConstraints = NO;
</code></pre>

If I do this the app crashes with

<blockquote>
 Auto Layout still required after executing -layoutSubviews.
 UITableView's implementation of -layoutSubviews needs to call super.
</blockquote>

OK, I thought you can't use auto layout on a table view header and only on the subviews. But that's not the full truth as you see it later. To sum up: Don't disable auto resizing mask for the header on iOS 7. Otherwise it's working fine.

iOS 8:

<pre><code>// you have to do this, otherwise you get an auto layout error
sectionHeader.translatesAutoresizingMaskIntoConstraints = NO;
</code></pre>

If I wouldn't use this I'd get the following output:

<blockquote>
 Unable to simultaneously satisfy constraints.
</blockquote>

For iOS 8 you have to disable auto resizing mask for the header.

Don't know why it behaves in this way but it seems that Apple did fix some things in iOS 8 and auto layout is working differently on iOS 7 and iOS 8.

blocks|key|5059|text|我在定制UITableViewHeaderFooterView+%2B+xib方面也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5060|我在这里看到了一些答案，但在我的自定义页脚视图类修复中发现了什么实现-layoutSubviews问题：|5061|-(void)layoutSubviews
{
++++[super+layoutSubviews];
++++[self+layoutIfNeeded];+//+this+line+is+key
}|code-block|syntax|javascript|5062|entityMap^0|4|R|0|Y|F|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

I had same trouble with custom <code>UITableViewHeaderFooterView</code> + xib.

I saw some answers here, but I found what implementation <code>-layoutSubviews</code> in my custom footer view class fixes issue:

<pre><code>-(void)layoutSubviews
{
 [super layoutSubviews];
 [self layoutIfNeeded]; // this line is key
}
</code></pre>

blocks|key|3902423|text|我也有过同样的问题。我转到我的DetailViewController并将标识符重命名为UIView。它以前在UITableView上。它解决了问题。这个问题不必出现在您的DetailViewController中。可能是在其他任何一个。尝试将其重命名为受人尊敬的标识符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3902424|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I went had the same issue. I went to my DetailViewController and renamed the identifier to UIView. It was previously on UITableView. It fixed the problem. This problem doesn't have to be in your DetailViewController. It could be in any other one. Try renaming it to the respected identifier.

blocks|key|5082|text|我在IB中的静态表视图单元格也有类似的问题。其中一个单元格有一个子视图，其类被错误地更改为UITextfield的子类。编译器没有给出任何警告/错误。但是在运行时，系统无法将上述崩溃加载到视图控制器中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5083|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a similar issue with static table view cells in IB. One of the cells had a subview that had a class that was mistakenly altered to a subclass of UITextfield. The compiler didn't give any warnings/errors. But at runtime the system was unable to load the view controller with the aforementioned crash as a result.

blocks|key|3881012|text|问题是对子视图的布局调用的顺序：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3881013|Check+out|offset|length|3881014|出现在iOS+<+8中|style|BOLD|3881015|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/29077172/4299011^0|0|0|9|0|0|3|7|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@$D|X|E|Y|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Issue is sequencing of the layout calls to the subviews:
<a href="https://stackoverflow.com/a/29077172/4299011">Check out</a>
Shows up in iOS &lt; 8

blocks|key|3902486|text|解决方案:调用超级layoutSubviews之前更改约束|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3902487|-+(void)layoutSubviews
{

++++[self+_updateConstraints];

++++[super+layoutSubviews];
}|code-block|syntax|javascript|3902488|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Solution:
change constraints before call super layoutSubviews

<pre><code>- (void)layoutSubviews
{

 [self _updateConstraints];

 [super layoutSubviews];
}
</code></pre>

blocks|key|5100|text|我修改了Carl+Lindberg's+answer以替代UITableView，它开始为我工作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5101|UITableView%2BAutoLayoutFix.h|BOLD|5102|@interface+UITableView+(AutoLayoutFix)
@end|code-block|syntax|javascript|5103|UITableView%2BAutoLayoutFix.m|5104|#import+<objc/runtime.h>

@implementation+UITableView+(AutoLayoutFix)

%2B+(void)load
{
++++Method+existingMethod+=+class_getInstanceMethod(self,+@selector(layoutSubviews));
++++Method+newMethod+=+class_getInstanceMethod(self,+@selector(_autolayout_replacementLayoutSubviews));

++++method_exchangeImplementations(existingMethod,+newMethod);
}

-+(void)_autolayout_replacementLayoutSubviews
{
++++[super+layoutSubviews];
++++[self+_autolayout_replacementLayoutSubviews];+//+not+recursive+due+to+method+swizzling
++++[super+layoutSubviews];
}

@end|5105|然后，在MyViewController.m中，我只是导入了这个类别：|5106|#import+"UITableView%2BAutoLayoutFix.h"|5107|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/12941256/426794^0|T|B|4|M|0|0|0|R|0|0|0|R|0|0|4|I|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|F|3|G|5|6|7|19|8|@$9|1A|A|1B|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1C|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1D|8|@$9|1E|A|1F|B|H]]|D|@]|E|$]]|$1|P|3|Q|5|K|7|1G|8|@]|D|@]|E|$L|M]]|$1|R|3|S|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|T|3|U|5|K|7|1K|8|@]|D|@]|E|$L|M]]|$1|V|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

I modified <a href="https://stackoverflow.com/a/12941256/426794">Carl Lindberg's answer</a> to override <code>UITableView</code> instead and it started working for me:

UITableView+AutoLayoutFix.h

<pre><code>@interface UITableView (AutoLayoutFix)
@end
</code></pre>

UITableView+AutoLayoutFix.m

<pre><code>#import &lt;objc/runtime.h&gt;

@implementation UITableView (AutoLayoutFix)

+ (void)load
{
 Method existingMethod = class_getInstanceMethod(self, @selector(layoutSubviews));
 Method newMethod = class_getInstanceMethod(self, @selector(_autolayout_replacementLayoutSubviews));

 method_exchangeImplementations(existingMethod, newMethod);
}

- (void)_autolayout_replacementLayoutSubviews
{
 [super layoutSubviews];
 [self _autolayout_replacementLayoutSubviews]; // not recursive due to method swizzling
 [super layoutSubviews];
}

@end
</code></pre>

Then in <code>MyViewController.m</code> I just imported the category:

<pre><code>#import "UITableView+AutoLayoutFix.h"
</code></pre>

blocks|key|3902584|text|我遇到了同样的问题，最后找到了--的原因是我向UITableViewCell添加了一个约束，这应该是UITableViewCell的contentView。当我改变约束时，一切都很好！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3902585|entityMap^0|F|2|1U|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I met the same problem and finally found the reason was that I added one constraint to the UITableViewCell, which should be the UITableViewCell's contentView. When I changed the constraint everything went fine!

Using XCode 4.5 and iOS 6, I'm developing an app with a simple table view with custom cells. I've done this a hundred times in iOS 5 and below, but for some reason the new autoLayout system is giving me a lot of trouble.

I setup my table view and prototype cell in IB, added subviews and wired them up as IBOutlets then setup my delegate and dataSource. However now whenever the first cell is fetched from <code>cellForRowAtIndexPath</code>, I get the following error:

<blockquote>
 *** Assertion failure in -[ShopCell layoutSublayersOfLayer:], /SourceCache/UIKit_Sim/UIKit-2372/UIView.m:5776
 
 *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Auto Layout still required after executing -layoutSubviews. ShopCell's implementation of -layoutSubviews needs to call super.'
</blockquote>

I haven't implemented a -layoutSubviews method in my subclassed cell (ShopCell), and even when I try to do that and add the super call as it suggests I still get the same error. If I remove the subviews from the cell in IB, and change it to a standard UITableViewCell, everything works as expected, though of course I'm left with no data in my cells.

I'm almost certain that there's something simple I'm missing, but can't find any documentation or guides to suggest what I've done wrong. Any help would be appreciated.

Edit: Just tried changing it to a UITableViewCell in IB and leaving all the subviews in place, still the same error.

"Auto Layout still required after executing -layoutSubviews" with UITableViewCell subclass

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

使用XCode 4.5和iOS 6，我正在开发一个带有自定义单元格的简单表视图的应用程序。在iOS 5和更低版本中，我已经做过一百次了，但是由于某种原因，新的autoLayout系统给我带来了很多麻烦。我在IB中设置了表视图和原型单元格，添加了子视图，并将它们连接为IBOutlets，然后设置我的委托和dataSour...

问带有-layoutSubviews子类的“执行-layoutSubviews后仍然需要自动布局”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带有-layoutSubviews子类的“执行-layoutSubviews后仍然需要自动布局”EN