States that an application can be in.
The values below describe notifications from the operating system. Applications should not expect to always receive all possible notifications. For example, if the users pulls out the battery from the device, no notification will be sent before the application is suddenly terminated, along with the rest of the operating system.
- WidgetsBindingObserver, for a mechanism to observe the lifecycle state from the widgets layer.
- inactive → AppLifecycleState
The application is in an inactive state and is not receiving user input.
On iOS, this state corresponds to an app or the Flutter host view running in the foreground inactive state. Apps transition to this state when in a phone call, responding to a TouchID request, when entering the app switcher or the control center, or when the UIViewController hosting the Flutter app is transitioning. Apps in this state should assume that they may be paused at any time.
On Android, this state is currently unused.
- paused → AppLifecycleState
The application is not currently visible to the user, not responding to user input, and running in the background.
Android apps in this state should assume that they may enter the suspending state at any time.
- resumed → AppLifecycleState
The application is visible and responding to user input.
- suspending → AppLifecycleState
The application will be suspended momentarily.
On iOS, this state is currently unused.
- values → List<AppLifecycleState>
A constant List of the values in this enum, in order of their declaration.