-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
404 HttpExceptions #504
Comments
I've encountered the same issue, any solution? |
me too :( |
My solution: |
@renefloor do you have any plans to take a look at that bug in near future? |
@renefloor, Probably it is possible to implement something like that? |
But this is just not trying to get the image when you don't have an internet connection. That would break the offline caching though. Getting the state from the ImageProvider to the Image widget needs to be done by throwing an exception. |
I just encountered this one too. |
I have the same problem now : ( |
Same problem here. |
I'm sorry, but there is not really a solution, as this is how Dart and Flutter works. I'm closing this issue because it is not fixable by this library. |
I have the same problem now |
Seeing the same issue as well. Any updates? |
This happens when calling a specific URL (such as an image posted on Github). Changing the URL address is the only solution. |
🔙 Regression
Old (and correct) behavior
When the URL is invalid(the image fails to load), the console print the error info once, and there are no exceptions.
Current behavior
When the URL is invalid(the image fails to load) and if there two more CachedNetwrokImage with that invalid URL, the following error info repetitively prints in the console, and then it will show the exceptions.
Screenshot
Error Info
Exception
Reproduction steps
create two more CachedNetworkImage widgets with the same invalid URL, and reload them a few times.
try to go to the image view screen a few times on the following example app, you will get the above issue.
Configuration
N/A
Version: 2.3.3
Platform:
The text was updated successfully, but these errors were encountered: