Jesse
Jesse
@jsappme I think your component needs a prop.
@jsappme Do any of the images break without CacheableImage ? meaning using regular Image ?
Hmm.. too many files maybe being written to storage at once ? maybe they need to be queued up for download.
@jsappme I think it could be that the image is destroyed even before it's had a chance to finish downloading. I believe if that occurs the cached file just needs...
@jsappme can you try the following please ``` diff --git a/image.js b/image.js index c53e479..4b13ff3 100644 --- a/image.js +++ b/image.js @@ -18,11 +18,12 @@ this.state = { isRemote: false, cachedImagePath: null,...
@jsappme if you can test the latest version.
@MossP have you tried the dev branch ? The component has to be restructured so that data logic can be extracted into its own module that facilitates loading and cache...
Sorry guys.. I haven't been able to maintain this package as much as I need to. I believe for the most part this package is now obsolete though may be...
yeah this has been requested.. I have to look into this.
Can you add the warning message you're receiving here?