Image was partially loaded but onLoad was called and onError (on iOS) was not called

[xzdev]

Issue Description

When using multiple <Image source='http://someImagePath' /> to load a bunch of network images, some user interaction triggers a navigation update which loads new scene to the top. When coming back to the previous scene, a few of images were partially loaded (as shown in the following picture).

Adding onLoad and onError (on iOS) to debug, I found onLoad was called and onError was never triggered. That means the broken image was considered as loaded successfully. As the partially loaded images were cached, even triggering another render will still show the broken images.

The issue was recently introduced around 0.28 and it is reproducible on the build 0.32 and 0.33.

Is there anyone who have the similar issue?

Additional Information

• React Native version: [0.32 & 0.33]
• Platform(s) (iOS, Android, or both?): [both]
• Operating System (macOS, Linux, or Windows?): [macOS]

[bitcoinvsalts]

+1

[wcandillon]

@xzdev Does this happens with remote image? This issue only happens to me for images which I save to the filesystem.

[xzdev]

Yes. It happens to me with remote images. It happens when there are multiple remote images loading concurrently and immediately navigate to a new scene. The issue did not occur again on my 6+ after upgrading to the latest IOS.

[relaxedtomato]

Has anyone found a resolution to this - I am noticing this on iOS 9 at the moment.

[relaxedtomato]

@jsappme, @wcandillon - did you research this bug further?

cc: @ptmt @mihailmetro

[bitcoinvsalts]

@r-bansal I was using a buggy image cache module

[wcandillon]

@r-bansal same for me!

[wcandillon]

@r-bansal @xzdev You can find more details about why this happens at wkh237/react-native-fetch-blob#331. This use case is supported in https://github.com/wcandillon/react-native-img-cache.

@shergin I think this issue can be closed.

[shergin]

@xzdev You are using react-native-img-cache, right?