-
Notifications
You must be signed in to change notification settings - Fork 43
SingleCollectionViewProvider<Cell: UICollectionViewCell> Does not conform protocol UniqueAnimatableCollectionViewProvider - Swift compiler error segmentation fault 11 #29
Comments
On a separate node (in case this is related) - After I "fixed" the protocol conformation issue, Flix will failed to compile in xcode 10.3 & swift 4.2 with a segmentation fault 11:
(skipping sensitive info)
|
Ok, looks like this is not going to get authors' attention any time soon But for the record, want to share my debug findings anyway, in case other people also using this is scrambling their head trying to fix the same thing.
|
Hi, @10000TB this error has fixed on 3.0.0. See 0734313#diff-7c7e5b8536101ffa202058a30b0416b9R86 . I'm not sure why cause "segmentation fault 11", look like Swift's bug. |
Or you can use this branch https://github.com/DianQK/Flix/tree/release/2.0.1. I cannot build this for iOS 9 with Xcode 10, and I'm not sure why "Flix did not pass validation" for pod lint. |
@DianQK To your first response - just verified that 3.0.0 does fix the protocol conformation issue (which seems to add onUpdate(..) right before configureCell(...)). but it still gives segmentation fault like following, and it looks like
|
@DianQK (Follow up from above - same using 3.0.0 branch) on a separate note, for the crash/swift compiler error Adding this piece code into
(code borrowed from |
(Accidentally clicked close - reopened it for @DianQK to make a decision on this) |
(Also updated title to include segmentation fault, hope that will direct people here when they ran into same issue in the description) |
For the linting issue - not sure what it is - but does not sound like a blocker if it is just style check |
I add some workaround methods. see #30 . |
👍 |
SingleCollectionViewProvider<Cell: UICollectionViewCell> Does not conform protocol "UniqueAnimatableCollectionViewProvider" in
UniqueCustomCollectionViewProvider.swift
- it used compile with no problem, any idea on why this is happening lately on 2.0.0 release ? @DianQKThe text was updated successfully, but these errors were encountered: