CachedImage with force-fetch parametter about react-native-cached-image

[kfiroo]

@ramsestom If you know you want to force fetch a url you could remove it from the cache and reload your image, that should do the trick

[manjeets12]

tried this but showing same image all the time even after it resolve successfully, I checked in browser and image is different

ImageCacheProvider.clearCache({cacheLocation: ImageCacheProvider.LOCATION.BUNDLE}).
    then(() => {
            console.log('cacheMultipleImages Done');
    })
    .catch(err => {
        console.log('cacheMultipleImages caught an error: ', err);
    });

[kfiroo]

@manjeets12 If you are using the latest v1.4.0 release, you could use ImageCacheManager.deleteUrl to invalidate a single url from the cache and force the cache manager to download it again.

v1.3.5 had ImageCacheProvider.deleteCachedImage that did the same thing.

[vonovak]

@kfiroo the point here is that if user changes the image on the server, this package doesn't fetch the new image but instead uses the old one...

[kfiroo]

@vonovak Thanks, that's why I suggested to use deleteUrl or deleteCachedImage to make sure the url will return the newly uploaded image and not the cached version :)

[vonovak]

sure @kfiroo but how can I tell whether or not the image on server has changed? - how to know whether I should call deleteUrl or deleteCachedImage? I could call it on every start, but that renders the cache useless. That's why @ramsestom suggested to have an option that would control how the caching works. For example, the package could make a HEAD request to the server to see if the locally stored image is out of date and download the new one if that is the case.. :)

[kfiroo]

@vonovak The original issue here is about adding a forceFetch prop to the CachedImage which means you have to know (on the client side) that the URL is out-of-date and the image should be fetched again, and for that end I suggested the deleteUrl method.

You raise a good point, though. In the scenario where the image changed on the server and there is an old cached version in the client's app there is no way for us to know it.

I would generally suggest to use the CachedImage for static URLs of images that you don't want to bundle with your app so you can download them once and make the app feel faster.

Regarding "controlling how the caching works", the latest version actually has all cache login injected into to the ImageCacheManager so you can customize if however you like, I would love to get some feedback if you do decide to try that approach :)