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

issue with the stalePeriod config

Open
#485 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the behavior with the shown CustomCacheManager class and its Config.stalePeriod value alongside cached_network_image. Trace how the cache manager is supplied to image loading and verify whether an image remains usable after the configured duration. Done means identifying the cause and making stalePeriod take effect, or documenting a confirmed limitation and required configuration.

Written by the indexing model from the issue text.

Description

I’ve encountered an issue with the stalePeriod setting in our CustomCacheManager when using it with cached_network_image. I tried setting different values, such as 1 minute, 1 day, and 15 days, but it doesn’t seem to take effect.

Here’s the current implementation:


class CustomCacheManager {
  static const key = 'customCacheKey';
  static CacheManager instance = CacheManager(
    Config(
      key,
      stalePeriod: const Duration(days: 15),
    ),
  );
}

I expected the cache to expire based on the stalePeriod value, but the images are still being loaded from cache beyond the set duration. Are there any limitations or additional configurations required for cached_network_image to respect this setting?

Would appreciate any insights. Thanks!

cached_network_image: ^3.4.1
flutter_cache_manager: ^3.4.1
flutter: 3.29.2

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.