Info | Value |
-------------------------|-------------------------------------|
Platform Name | iOS
Platform Version | 12.0 beta
SDWebImage Version | 4.4.0 (master)
Integration Method | manually
Xcode Version | Xcode 10.0 beta
Repro rate | all the time (100%)
Repro with our demo prj | You can see in Demo project in this repo
Demo project link | https://github.com/rs/SDWebImage/tree/master/Examples/SDWebImage%20Demo
In iOS 12.0 beta, WebP image download cannot display.
In demo project in this repo, the image 3 and 4, which are WebP image, might be empty as below.

image 5 - 7 are also WebP, but these are gif images so that see as well.
Try the lastest version (4.4.0) firstlly. Not the previous release

@dreampiggy Sorry for my misunderstanding, this is occurred on the latest.
@d-date Seems works on the iPhone simulator. Does this cause issue on the real device ? Because libwebp for ARMv64 device using the NEON optimization. Where the iPhone Simulator is x86 device. I guess maybe it's related to this.
I will find a real device running iOS 12.0 beta firstlly.
@dreampiggy Yes, I've checked on my iPhoneX and also happened.
This is run on my iPhone X.
@d-date Did you try the 5.x branch for this as well ? It seems I need some time to get a extra test iPhone and upgrade to iOS 12... 馃槄
@dreampiggy 5.x branch works well for me!
Simulator:

Physical Device (iPhone X):
@d-date Conformed seems a bug that because of using the wrong arg in CGImageCreate. However, this seems does not cause issue in the previous iOS release 馃槄
It also happend on the iPhone Simulator. Sorry that I previous using the 5.x branch for testing but not the master branch. 5.x branch using another bitmapInfo for a little performance consideration, so it does not cause this issue.
See #2348
@d-date You can test the master branch now. It should been fixed.
@dreampiggy LGTM馃槑I tested on Simulator and my iPhone X and works well! Thank you for your great job!
4.4.1 version release. Anyone here please upgrade if you're using WebP images 馃槂
Hello guys,
I am facing the same problem. v4.4.1 - Whose version are you talking about?
What should I do to get away from this issue?