Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

The failed loading status should not be cached. #930

Open
2 tasks done
windinternet opened this issue Mar 8, 2024 · 1 comment
Open
2 tasks done

The failed loading status should not be cached. #930

windinternet opened this issue Mar 8, 2024 · 1 comment

Comments

@windinternet
Copy link

windinternet commented Mar 8, 2024

馃悰 Bug Report

There are many reasons for image loading failure, but it is inevitable that the loading will fail due to objective network congestion or busy service. This failure status should not be cached, because when the network recovers, I hope to try loading again, because it has already Once it is cached, it will no longer make actual requests. Only by manually clearing the cache can the actual load be carried out again. However, ordinary users will not think in this direction. Even if they know the reason, they will not know how to clear the cache.

Expected behavior

Only successfully loaded images should be cached

Reproduction steps

  1. Prepare a picture server and get the URL of one of the pictures.
  2. Close the image server
  3. Use widgets to load this url
  4. Start the image server
  5. Then use the widget to load the url

Configuration

Version: 1.x

Platform:

  • 馃摫 iOS
  • 馃 Android
@AntFate
Copy link

AntFate commented Mar 27, 2024

Same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants