Skip to content
cccskills
FreePublished on GitHub

flutter-dispose-timer-test-failure

Fix Flutter test failure "A Timer is still pending even after the widget tree was disposed". Use when: (1) Widget tests fail with timer pending error, (2) dispose() contains Future(), Future.delayed(), or Timer calls, (3) Riverpod provider modifications in dispose(). The fix is to use deactivate() instead of dispose() for cleanup that might trigger async work.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile
See how to install

Files included (1)

  • SKILL.md3.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Flutter Dispose Timer Test Failure

Problem

Flutter widget tests fail with the error "A Timer is still pending even after the widget tree was disposed" when dispose() contains Future-based cleanup code.

Context / Trigger Conditions

  • Test error: A Timer is still pending even after the widget tree was disposed
  • Widget's dispose() method contains:
    • Future(() => ...)
    • Future.delayed(...)
    • Timer(...) or Timer.periodic(...)
    • Riverpod ref.read(provider.notifier).someMethod() wrapped in Future
  • Tests pass individually but fail when run together
  • Error appears at end of test, not during widget interaction

Solution

Step 1: Identify the problematic code

Look for patterns like this in your widget:

// BAD: Creates pending timer that test framework detects
@override
void dispose() {
  final notifier = _overlayNotifier;
  if (notifier != null) {
    Future(() => notifier.setSettingsOpen(false));  // <- Problem!
  }
  super.dispose();
}

Step 2: Move cleanup to deactivate()

Use deactivate() instead of dispose() and remove the Future wrapper:

// GOOD: Runs synchronously before widget is removed
@override
void deactivate() {
  _overlayNotifier?.setSettingsOpen(false);  // Direct call, no Future
  super.deactivate();
}

Step 3: Understand the lifecycle difference

  • deactivate(): Called when widget is removed from tree, but State might be reinserted
  • dispose(): Called when State will never build again, permanent cleanup

For most notification/provider cleanup, deactivate() is appropriate.

Verification

  1. Run the specific test that was failing
  2. Run the full test suite
  3. Verify no "Timer is still pending" errors

Example

Before (causes test failure):

class _SettingsScreenState extends ConsumerState<SettingsScreen> {
  OverlayNotifier? _overlayNotifier;

  @override
  void dispose() {
    final notifier = _overlayNotifier;
    if (notifier != null) {
      // This Future creates a pending timer!
      Future(() => notifier.setSettingsOpen(false));
    }
    super.dispose();
  }
}

After (tests pass):

class _SettingsScreenState extends ConsumerState<SettingsScreen> {
  OverlayNotifier? _overlayNotifier;

  @override
  void deactivate() {
    // Synchronous call, no timer created
    _overlayNotifier?.setSettingsOpen(false);
    super.deactivate();
  }
}

Notes

  • The original Future(() => ...) pattern is often used to defer provider modifications until after the current build phase, avoiding "Cannot modify provider during build" errors
  • If you need deferred execution, consider WidgetsBinding.instance.addPostFrameCallback instead, though this also creates timers that can fail tests
  • For Riverpod, modifying providers in deactivate() is usually safe since the widget tree is being torn down, not built
  • This issue often surfaces when multiple tests run sequentially, as the test framework checks for pending timers between tests

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

argocd-externalsecret-namespace-permission

Free

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 20, 2026

art-direct

Free

Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 20, 2026

async-await-null-race-condition

Free

Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 20, 2026

aws-v4-signing-custom-headers-gcs

Free

Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 20, 2026

bash-herestring-newline-secrets

Free

Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 20, 2026

blossom-content-addressed-url-filtering

Free

Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 20, 2026

See all skills by divinevideo

Report a problem with this skill