Fix iOS 13 compatibility && WebImage/AnimatedImage using @State to publish changes #232
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.
Changes
ImageManager
API changes. Theinit
method has no args, useload(url:options:context:)
insteadThis PR close #230 close #229 close #228
As for now, Swift still can not use different stored property on different availability check OS Host. This is runtime limit. Previous #227 will cause a Swift runtime crash when demangling symbols from iOS 13+
So, I just remove the
SwiftUI.StateObject
references and use Backport + PlatformAppear hack (BecauseSwiftUI.List
'sonAppear
does not works as expected when using nonSwiftUI.StateObject
)v3.0.0 will remove iOS 13 support.