riverpod-cancel

To cancel in-flight Riverpod async requests, use auto-dispose providers and register ref.onDispose to close the HTTP client created inside the provider. This automatically aborts pending calls when the user leaves the page.

The best way to debounce rapid refreshes in Flutter Riverpod is to introduce a delay before issuing requests, coalescing redundant triggers. This prevents unnecessary work when users trigger rapid updates.

Riverpod HTTP clients leak because they are not properly disposed when navigating away. To fix this, instantiate the HTTP client inside an auto-dispose provider and register ref.onDispose to close it.

Yes, auto-dispose providers are required for resource cleanup in Riverpod. They enable the ref.onDispose callback, which closes HTTP clients or cancels streams automatically when the provider is no longer needed.

You can implement resource cleanup and debouncing together in Riverpod by combining ref.onDispose for client closure with a delay mechanism to coalesce rapid user actions, ensuring efficient async request handling.