-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offline cache image isn't download the image from the same Url #20
Comments
Hi, Can you try re-fetch the image by specifying 'reloadImage={true}'. Irrespective of the image already being stored offline, this way you can refresh/load the most recently updated images. Please let us know if it helps. |
The problem is not in the loading of the offline stored image but when we download it by using preload from the url. |
Hi, Does it show the fallback image or does it show any errors in the console? Could you provide more information so we can help you more efficiently? Also, please check potential CORS issues. |
This is my .js class where i am using offline image store, It calculates the total number of urls and then bind them into an array after that it downloads all of the images from the array. Then we are showing the downloading process in the text by dispatching an action. When we run the code for the very first time it works fine but second time. It stuck at some point and the downloading text also shows the stopped downloading. Check the following code :-
|
Can you check if the problem still exists in V0.1.9? Thank you! |
Hi, i am using offline image cache storage to store images offline but i am facing an issue that is the library isn't able to download the image from the same url which is stored already in the cache.
For example:- https://images.graph.cool/v1/cji4f30yf6uwx0119va5jp226/cjio9y0ny7sat0161stutdvts/800x600
This is the url and when i call the offline image store again to download and store it in the offline that is not stored even i cleared the offline image cache.
Please give the solution.
The text was updated successfully, but these errors were encountered: