An app can be placed into different queues that each order the app to perform different activities. You need to manage these run partitions to ensure the app behaves correctly.
There are three run partitions for an app: foreground, background, and stopped. Each of these distinct run partitions represent queues that an app can be placed into. When the Adaptive Partition Scheduler moves the app to a different partition, the navigator event, NAVIGATOR_APP_STATE , is sent to notify the app about the change.
The foreground partition is entered when your app is running in the foreground. The app is in the full screen state and is considered to be the main app on the device.
The background partition is entered when your app is sent to the background. The navigator event is sent with the notification of this partition when, for example, the app is moved from the full screen state to the thumbnail state. The app may still be running if given the permission run_when_backgrounded.
The stopped partition is entered shortly after the NAVIGATOR_APP_STOPPING event is received. The stopped partition means the app is not running and is not visible.
You need to manage your app as it moves among these partitions.