tableView.cellForRowAtIndexPath(indexPath) return nil

邮差的信 提交于 2019-12-23 09:33:46

问题


I got a validation function that loop through my table view, the problem is that it return nil cell at some point.

for var section = 0; section < self.tableView.numberOfSections(); ++section {
    for var row = 0; row < self.tableView.numberOfRowsInSection(section); ++row {
        var indexPath = NSIndexPath(forRow: row, inSection: section)
        if section > 0 {
            let cell = tableView.cellForRowAtIndexPath(indexPath) as! MyCell
            // cell is nil when self.tableView.numberOfRowsInSection(section) return 3 for row 1 and 2
            // ... Other stuff
        }
    }
}

I'm not really sure what I'm doing wrong here, I try double checking the indexPath row and section and they are good, numberOfRowsInSection() return 3 but the row 1 and 2 return a nil cell... I can see my 3 cell in the UI too.

Anybody has an idea of what I'm doing wrong?

My function is called after some tableView.reloadData() and in viewDidLoad, is it possible that the tableview didn't finish reloading before my function is executed event though I didn't call it in a dispatch_async ??

In hope of an answer. Thank in advance

--------------------------- Answer ------------------------

Additional explanation :

cellForRowAtIndexPath only return visible cell, validation should be done in data model. When the cell is constructed in

override func tableView(tableView: UITableView, cellForRowAtIndexPath indexPath: NSIndexPath) -> UITableViewCell {

It should change itself according to the validation state.


回答1:


As stated in the documentation, cellForRowAtIndexPath returns:

An object representing a cell of the table, or nil if the cell is not visible or indexPath is out of range.

Hence, unless your table is fully displayed, there are some off screen rows for which that method returns nil.

The reason why it returns nil for non visible cells is because they do not exist - the table reuses the same cells, to minimize memory usage - otherwise tables with a large number of rows would be impossible to manage.




回答2:


I too experienced the issue where cellForRowAtIndexPath was returning nil even though the cells were fully visible. In my case, I was calling the debug function (see below) in viewDidAppear() and I suspect the UITableView wasn't fully ready yet because part of the contents being printed were incomplete with nil cells.

This is how I got around it: in the viewController, I placed a button which would call the debug function:

public func printCellInfo() {
    for (sectionindex, section) in sections.enumerated() {
        for (rowIndex, _) in section.rows.enumerated() {
            let cell = tableView.cellForRow(at: IndexPath(row: rowIndex, section: sectionindex))
            let cellDescription = String(describing: cell.self)

            let text = """
            Section (\(sectionindex)) - Row (\(rowIndex)): \n
            Cell: \(cellDescription)
            Height:\(String(describing: cell?.bounds.height))\n
            """

            print(text)
        }
    }
}

Please note that I'm using my own data structure: the data source is an array of sections, each of them containing an array of rows. You'll need to adjust accordingly.

If my hypothesis is correct, you will be able to print the debug description of all visible cells. Please give it a try and let us know if it works.



来源:https://stackoverflow.com/questions/31188893/tableview-cellforrowatindexpathindexpath-return-nil

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!