This repository has been archived by the owner on Feb 2, 2023. It is now read-only.
[ASCollectionView] Add strong Layer Pointer Under iOS < 9 to Workaround Crashes #1861
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.
Under iOS < 9, when a collection view is removed from the hierarchy and being prepared for deallocation, its layer may become a dangling pointer and put the collection view into a dangerous state where pretty much any call will crash.
This shouldn't be possible, since views are supposed to retain their layers, but it happens all the same. This adds a separate strong pointer to ASCollectionView to workaround the issue.
This issue is not technically ASDK-specific, but under ASDK it is far more likely to manifest because of the fact that ASDisplayNode intentionally keeps self alive for the next run loop turn in -didExitHierarchy