Fix for iOS 15 cell lifecycle behavior change #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Capture cell reference and load/reload cell resources on
willDisplayCellas a fix for iOS 15 cell prefetching behavior change.Background: On iOS 15+, for performance reasons, the table view data source may not recreate a cell using the
cellForRowmethod if there's a cached cell for the given IndexPath. In this case, it'll just callwillDisplayCell. However, we release a reference of the cell and cancel requests ondidEndDisplayingCell.So, since
cellForRowmay not be called anymore, we need to implementwillDisplayCellto know when the cached cell is becoming visible again to recapture a reference of the cell and load/reload any resource needed for the cell.