heightforrowatindexpath

iOS8 – constraints ambiguously suggest a height of zero

Forcing a return height and estimated height made the warning disappear in my case. – (CGFloat)tableView:(UITableView *)tableView estimatedHeightForRowAtIndexPath:(NSIndexPath *)indexPath { return 44; } – (CGFloat)tableView:(UITableView *)tableView heightForRowAtIndexPath:(NSIndexPath *)indexPath { return 44; } Another solution where you don’t need the two overrides is simply to use self.tableView.rowHeight = 44; in your loadView or init method.

Iphone – when to calculate heightForRowAtIndexPath for a tableview when each cell height is dynamic?

The way Apple implements UITableView is not intuitive to everyone and it’s easy to misunderstand the role of heightForRowAtIndexPath:. The general intention is that this is a faster and light-on-memory method that can be called for every row in the table quite frequently. This contrasts with cellForRowAtIndexPath: which is often slower and more memory intensive, … Read more