Bad state: called ProviderSubscription.read on a subscription that was closed about riverpod

[rrousselGit]

This is expected. The ProviderSubscription was already closed my Riverpod by the time you called .read()

Riverpod closes all subscriptions associated to a widget when the widget is unmounted. So you cannot use sub.read() after the widget got unmounted – which is what you do here.

[rrousselGit]

Sounds like you used Future to cheat around the error. That wasn't really supported

Looks like Consumer supports calling sub.read inside ConsumerState.dispose. Sounds like we would want to support this for useEffect.
Do you mind opening a feature request for this?

[a1573595]

This is expected. The ProviderSubscription was already closed my Riverpod by the time you called .read()

Riverpod closes all subscriptions associated to a widget when the widget is unmounted. So you cannot use sub.read() after the widget got unmounted – which is what you do here.

So there is currently no other solution to cache data?

I hope not to load all the DataSource at once when entering NextPage, and release the KeepAliveLink of DataSource after leaving NextPage.

[rrousselGit]

The issue is likely your Future wrapping the .read()

I guess removing it should work

[a1573595]

The issue is likely your Future wrapping the .read()

I guess removing it should work

I thought so before, but actually it's not.

Removing the future wrapping throws an error：

• 2.5.1：Bad state: called ProviderSubscription.read on a subscription that was closed.
• 2.4.10：At least listener of the StateNotifier Instance of 'StateController' threw an exception
  when the notifier tried to update its state.

Having a Future throws an error：

• 2.5.1：Bad state: called ProviderSubscription.read on a subscription that was closed.
• 2.4.10：Work well.