Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

url 404 and retry always 404

Open
#473 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
dart, flutter
Domain
mobile-dev

Research direction

Start with the CachedNetworkImage entry point, especially its errorListener, errorWidget, and refresh behavior after _syncImage calls setState. Reproduce the sequence where the initial URL returns 404, the URL is synchronized, and the widget is refreshed; done means the refreshed image no longer reports the cached 404 when the URL is available.

Written by the indexing model from the issue text.

Description

💬 Questions and Help

Here I'm using cached_network_image to loading network image. It may not exists with the giving image url, when I get 404 from errorListener, I async image to the url to make sure url is available. After that I refresh the CachedNetworkImage, still get error 404 from errorWidget.

Widget imgWidget() {
  return CachedNetworkImage(
    imageUrl: _imageUrl,
    imageBuilder: (context, imageProvider) {
      return Container(
        decoration: BoxDecoration(
          image: DecorationImage(
            image: imageProvider,
            fit: widget.fit,
          ),
        ),
      );
    },
    placeholder: (context, url) {
      return widget.placeholder;
    },
    errorWidget: (context, url, error) {
      return widget.placeholder;
    },
    errorListener: (e) {
      if (e is HttpException) {
        logger.d('----- errorListener ${e.uri.toString()} - ${e.message}');
        if (e.message.contains('404')) {
          _syncImage();
        }
      } else {
        logger.d('Image Exception is: ${e.runtimeType}');
      }
    },
  );
}

_syncImage() async {
  HttpManager().syncImageToCdnUrl(_imageUrl).then((_) {
    setState(() { });
  }).catchError((onError) {
    logger.d(onError);
  });
}
  
Dominant language
Dart
Stars
810
Forks
510
Avg merge
2d 2h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Baseflow/flutter_cache_manager

All issues in Baseflow/flutter_cache_manager

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.