Inconsistency in AppLifecycleState Detection Between iOS and Android in Flutter Hooks

[motucraft]

Inconsistency in AppLifecycleState Detection Between iOS and Android in Flutter Hooks

[rrousselGit]

You could use useOnAppLifecycleStateChange

[motucraft]

Would the following issues be relevant?
flutter/flutter#114756

I would like to detect AppLifecycleState because I want to cancel the Firestore snapshot once the app has moved to the background. (I'm using cloud_firestore_odm and riverpod.)

[rrousselGit]

The expected behavior is that on both iOS and Android platforms, transitioning the app to the background should consistently trigger AppLifecycleState.resumed, AppLifecycleState.inactive, and AppLifecycleState.paused in that order.

It is not possible to make this guarantee
Flutter decides when it invoked build. It could very well be that two life-cycle changes happen at once, before build could be invoked.
This would swallow the first event.

[motucraft]

I see, thanks your reply.

I would like to detect AppLifecycleState because I want to cancel the Firestore snapshot once the app has moved to the background. (I'm using cloud_firestore_odm and riverpod.)

Any ideas on this?

[motucraft]

That build may not be called means that it can only be handled within a callback, right?
I decided to respond in this way.

    useOnAppLifecycleStateChange((_, current) {
      switch (current) {
        case AppLifecycleState.resumed || AppLifecycleState.inactive:
          FirebaseFirestore.instance.enableNetwork();
          break;
        default:
          FirebaseFirestore.instance.disableNetwork();
      }
    });