Cellforrowatindexpath when is it called

EDIT: The method doesn't get called. Got it! At my position I had the tableview on my whole uiview and after click on "Add Missing Constraints", it will add this here: And now if you delete one of the Trailing or Leading Alignments, it will work - cellforrowatindexPath will get called!

Hope I can help you. Default initializers are removed from some imported enum types in Swift 3. Trav L. For completeness in case anyone has this strange situation. Only authorized users can answer the question. Please sign in first, or register a free account. Not the answer you're looking for?

Browse other questions tagged : uitableview. Ask Question. Asked 5 years, 7 months ago. Active 5 years, 7 months ago. Viewed 3k times. Improve this question. Pulkit Sharma Pulkit Sharma 1 1 gold badge 4 4 silver badges 18 18 bronze badges.

When you scroll the UITableView the method is again invoked to update the new rows. Add a comment. Active Oldest Votes. Every time you scroll and are about to see a new cell. UITableview uses the cell that is going out of the view visible area , and uses that particular cell to populate new data. After numberOfRows. If your View Controller has a tableview in the storyboard. This is called in viewDidLoad as when the VC inspects a tableview in the storyboard, it will call the mandatory tableview datasource numberOfRows first and then it will call cellForRowAtIndexpath , that amount of time, the number of cells visible in the screen.

Hope could solve your confusion. Improve this answer. Saheb Roy Saheb Roy 5, 2 2 gold badges 20 20 silver badges 35 35 bronze badges.

This method will called for the number of time for your number of cell visible. Suppose current 4 cell visible row0,row1,row2,row3. It again for 4 time for row Not sure why this breaks between iOS8 and iOS9 though.

I'm also not sure this is a long term fix but works. I prefer to solve this sort of thing by a making the logic such as you have in layoutSubviews not care about whether or not the property is nil i. If there are multiple properties to set, and the work of responding to property changes is expensive, then I'll define a separate method that the "parent" must call to refresh the UI after setting all the properties.

I believe this approach would be more robust as it doesn't depend on any implementation details such as when layout is performed. Search by keywords or tags Submit Search Clear search query Additional information about Search by keywords or tags Supported Searches:.