* Bump the dependency of SDWebImage into 5.8+ because of the SDWebImageDownloaderRequestModifier convenient API usage
* Fix the implementation on iOS for per-image-request-header-setup. Should not use `SDWebImageDownloader` which manage the global shared headers. Use the context option of request modifier.
* Add the support for data:image URL for WebP images
* Alaways bypass invalid SSL certificate error, same behavior like React-Native itself
* Fix the implementation of request modifier on SDWebImage, which have bugs on 5.8.0 (will fix in 5.8.1), revert the dependency bump
* Revert the changes to bypass SSL error
* Remove the unused Podfile.lock changes
This uses SDAnimatedImageView instead of FLAnimatedImageView for better animation support.
BREAKING CHANGE: Upgrade SDWebImage, may affect some projects and CocoaPods users.
Fix the bug of `cacheOnly` behavior
fix#447
It's recommended to never retain the strong reference to self into blocks.
Blocks maintain strong references to any captured objects, including self, which means that it’s easy to end up with a strong reference cycle.
[skip release]
Setting properties from JS to native components does not guarantee any
order (as far as I know). Because of this, `setSource` can get called
and complete before `setOnFastImageLoad` and `setOnFastImageLoadEnd`,
which results in the callbacks never firing.
This change implements a simple check for these callback properties
getting set after the image has loaded, and fires them at that time.
Setting properties from JS to native components does not guarantee any
order (as far as I know). Because of this, `setSource` can get called
and complete before `setOnFastImageLoad` and `setOnFastImageLoadEnd`,
which results in the callbacks never firing.
This change implements a simple check for these callback properties
getting set after the image has loaded, and fires them at that time.
Numan