android: `<Image>` component caches `file://...` even when it has been deleted

[msbit]

android: `` component caches `file://...` even when it has been deleted

[deepanshushuklad11]

@msbit @cortinico I did a bit of debugging .
In android we are using Fresco for images, after fetching image from Disk it caches it in memory .
So even if you delete the file from disk it will be served direct from bitMapMemoryCache.
We can test it adding this in ReactImageView.java

     Fresco.getImagePipeline().evictFromMemoryCache(mImageSource.getUri()); // mImageSource.getUri() is the image url
     Fresco.getImagePipeline().evictFromDiskCache(mImageSource.getUri());

I propose we should provide a method like Image.deleteCache([uri])
So that user can control what need to be served from disk or cache
Let me know your thoughts, i am happy to raise a PR for the same.

[cortinico]

Thanks for the investigation @deepanshushuklad11

     Fresco.getImagePipeline().evictFromMemoryCache(mImageSource.getUri()); // mImageSource.getUri() is the image url
     Fresco.getImagePipeline().evictFromDiskCache(mImageSource.getUri());

The user can just invoke these methods instead if they need to evict the cache. We don't need an API on React Native to do so (hence I'm closing this).

I would argue that you should instead opne a issue against facebook/fresco to ignore caching for file://* URIs.