Before you you resort to the clever but dangerous trick (shown in some of the answers) that masks the error by overriding the layoutSubviews() method of the table delegate or controller, I'd advise reviewing fundamentals and related documentation for how the table view is constructed and invoked, particularly if a navigation stack is involved. Make sure you're applying the right design pattern in the first place before trying to tackle the obscure downstream consequences of using the wrong paradigm, like I did.
This error was happening to me when I erroneously configured a UITableView delegate (UIViewController) as a tab on the app's root view controller, which I'd made a UITabBarController. In addition to the message quoted in the original question, I was seeing controller "not pushed " errors in the XCode console.
The problems went away after I implemented the approach documented in Apple's document "Combined View Controller Interfaces"
My incorrect approach had been to add the UITableView delegate (UIViewController) directly to the tab bar controller, then use performSegue() in the table delegate's 'didSelect' for index method. I was also using performSegue() as the action of the "+" icon I added to the UINavigationItem (which I obtained from the navigationItem property of UIViewController). The segues invoked the next viewController I'd written to handle (or create) table-related items.
The proper way to do it is to instead add a UINavigationController to the tab bar, not the table view delegate (or table view controller) to the tab bar. Then, add the table view delegate (or table view controller) to the navigation controller. And instead of using performSegue() in the table view delegate's "didSelectRowAt" method use navigationController?.pushViewController() (same for invoking the next navigation item based controller from a button outside the table view instead of a row inside).
Of course the proper way makes more sense, particularly since since my table view was playing with the UINavigationItem components and had configured itself to be used with a navigation bar anyway.
One other note: The error message shown in the question mentions adding a symbolic breakpoint to a certain method to see what's causing the problem. Of course that stops the code and shows a screen with assembly language that will be completely inscrutable to people working with distribution libraries instead of iOS source code that Apple insider's use. So if you try that, you'll want to use 'bt' at the lldb prompt to get the stack backtrace. In my case, all it showed me was that everything started with a tab button press and looked normal and expected. So the problem in my case just came down to a noob ignorance about how some of the pieces go together.