Why am I getting a “Auto Layout still required after executing -layoutSubviews” error every time my app launches now?

Since I added the following code, every time my app opens this UITableViewController it crashes:

 self.noArticlesView = [[UIView alloc] init];
 self.noArticlesView.translatesAutoresizingMaskIntoConstraints = NO;
 self.noArticlesView.backgroundColor = [UIColor colorWithRed:0.961 green:0.961 blue:0.961 alpha:1];

 [self.view addSubview:self.noArticlesView];

 [self.view addConstraint:[NSLayoutConstraint constraintWithItem:self.noArticlesView attribute:NSLayoutAttributeTop relatedBy:NSLayoutRelationEqual toItem:self.view attribute:NSLayoutAttributeTop multiplier:1.0 constant:0.0]];
 [self.view addConstraint:[NSLayoutConstraint constraintWithItem:self.noArticlesView attribute:NSLayoutAttributeBottom relatedBy:NSLayoutRelationEqual toItem:self.view attribute:NSLayoutAttributeBottom multiplier:1.0 constant:0.0]];
 [self.view addConstraint:[NSLayoutConstraint constraintWithItem:self.noArticlesView attribute:NSLayoutAttributeLeading relatedBy:NSLayoutRelationEqual toItem:self.view attribute:NSLayoutAttributeLeft multiplier:1.0 constant:0.0]];
 [self.view addConstraint:[NSLayoutConstraint constraintWithItem:self.noArticlesView attribute:NSLayoutAttributeTrailing relatedBy:NSLayoutRelationEqual toItem:self.view attribute:NSLayoutAttributeRight multiplier:1.0 constant:0.0]];    

And it gives me this error:

  • ChromeCast background video playback support iOS
  • iOS long-running background timer with “location” background mode
  • How to add QLPreviewController as Subview in objective C
  • Increment UISlider by 1 in range 1 to 100
  • Minimum Xcode version to upload to App store (As on February 2016)
  • ios 8 UITableViewCell detail text not correctly updating
  • * Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘Auto Layout still required after executing -layoutSubviews. UITableView’s implementation of -layoutSubviews needs to call super.’

    What on earth am I doing wrong? I call that code in tableView:numberOfRowsInSection: when there’s 0 rows.

    9 Solutions Collect From Internet About “Why am I getting a “Auto Layout still required after executing -layoutSubviews” error every time my app launches now?”

    I was subclassing UIScrollView and received the same error message on iOS 7 (but not 8).

    I was overriding layoutSubviews in a manner similar to the following:

    - (void)layoutSubviews {
        [super layoutSubviews];
        // code to scroll the view

    I resolved the issue by moving the call to super’s layoutSubviews to be the last thing in the method:

    - (void)layoutSubviews {
        // code to scroll the view
        [super layoutSubviews];

    Had the same problem. Added view(s) to self.tableView and used constraints. Do not add the views to the table view via addSubview: but add them as header(s), footer(s) or cells.

    [self.view layoutIfNeeded]

    Hope this helps

    You also need to disable mask translation for the table view.

    for me is was this

    self.tableView.backgroundView = self.emptyView;

    I changed to this

        NSComparisonResult order = [[UIDevice currentDevice].systemVersion compare: @"8.0" options: NSNumericSearch];
    if (order == NSOrderedSame || order == NSOrderedDescending) {
        // OS version >= 8.0
        self.tableView.backgroundView = self.emptyView;
        [self.tableView.backgroundView addSubview:self.emptyView];

    Checkout "Auto Layout still required after executing -layoutSubviews" with UITableViewCell subclass as the question appears to be the same.

    I was able to implement the category mentioned in one of the answers which solved the problem for me. However, I had to create the category on the UITableView class instead of the UITableViewCell class as is discussed in that particular answer.

    You can add your ‘no articles view’ as a custom header in the table to make sure it’s positioned correctly.

    A possible solution is not to add the noArticlesView directly in the table, but is to put the UITableView inside a container UIView (eventually setting table constraints to fit with the container frame) and then constraint your noArticlesView to the container, using the same constraints you set and in the same place in your code, that is inside the -tableView:numberOfRowsInSection: UITableViewDataSource method.
    I tested it with a simple example, and it worked.
    The changes you need to apply to your code are to replace the UITableViewController with a UIViewController, add a container view (unless you want your table to fit exactly with the view controller’s view, in such case this view is the container) and then constraint your noArticleView to the container instead of the table.
    My example code is at the bottom of this answer.
    I will try to make a possible explanation of the reason of the issue and why this solution works, but consider that part of my explanation is based on guesses so it couldn’t be completely exact.
    First of all a brief explanation of how the view hierarchy rendering process works in iOS. The first step for the layout engine is to determine the size and position of all views and subviews in the view hierarchy. Usually this is done with an iterative approach, where auto layout constraints are evaluated, in order to determine size and position of views and subviews, and then each view’s -layoutSubviews method is called for fine tuning: this means that you can change your layout after constraints are evaluated. What the layout engine requires is that if the -layoutSubviews method changes constraints again, then -[super layoutSubviews] must be called again to allow the iterative process: if this doesn’t happen the layout engine raises an exception. In the case of the UITableView my guess is that the tableView:numberOfRowsInSection: method is called somewhere within the internal UITableView layoutSubviews method and this method doesn’t call [super layoutSubviews]. So if your table data source method updates internal table constraints, at the end of the method the exception is triggered. The solution I propose works because the only constraint applied to the table is the external constraint towards the container, so evaluated at the first stage of the layout process, while the constraints added in the table data source method are not relevant to the table as they are applied to views external to the table (container and noArticlesView) so they don’t affect the internal table view layout process.

    //  RootController.h
    @interface RootController : UIViewController
    @property (nonatomic,strong) IBOutlet UITableView *table;
    @property (nonatomic,strong) IBOutlet UIView *container;
    //  RootController.m
    #import "RootController.h"
    @implementation RootController
    #pragma mark - Table view data source
    - (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
        // Return the number of sections.
        return 1;
    - (NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section
        // Return the number of rows in the section.
        UIView *_v = [[UIView alloc] init];
        _v.backgroundColor=[UIColor redColor];
        [self.container addSubview:_v];
        NSLayoutConstraint *_c1 = [NSLayoutConstraint constraintWithItem:_v
                                                                attribute:NSLayoutAttributeTop relatedBy:NSLayoutRelationEqual toItem:self.container attribute:NSLayoutAttributeTop multiplier:1.0 constant:20.0];
        NSLayoutConstraint *_c2 = [NSLayoutConstraint constraintWithItem:_v
                                                               attribute:NSLayoutAttributeBottom relatedBy:NSLayoutRelationEqual toItem:self.container attribute:NSLayoutAttributeBottom multiplier:1.0 constant:-20.0];
        NSLayoutConstraint *_c3 = [NSLayoutConstraint constraintWithItem:_v
                                                               attribute:NSLayoutAttributeLeading relatedBy:NSLayoutRelationEqual toItem:self.container attribute:NSLayoutAttributeLeft multiplier:1.0 constant:20.0];
        NSLayoutConstraint *_c4 = [NSLayoutConstraint constraintWithItem:_v
                                                               attribute:NSLayoutAttributeTrailing relatedBy:NSLayoutRelationEqual toItem:self.container attribute:NSLayoutAttributeRight multiplier:1.0 constant:-20.0];
        [self.container addConstraints:@[_c1,_c2,_c3,_c4]];
        return 0;

    I unchecked auto layout on the view controller the crash is not occurring now