Mission Management and Launch Type (for System Applications Only)
One UIAbility instance corresponds to one mission. The number of UIAbility instances is related to the UIAbility launch type, specified by launchType, which is configured in the config.json file in the FA model and the module.json5 file in the stage model.
The following describes how the mission list manager manages the UIAbility instanced started in different modes.
-
singleton: Only one UIAbility instance exists for an application.
Figure 1 Missions and singleton mode

-
multiton: Each time startAbility() is called, a UIAbility instance is created in the application process.
Figure 2 Missions and multiton mode

-
specified: The (onAcceptWant()) method of AbilityStage determines whether to create a UIAbility instance.
Figure 3 Missions and specified mode

Each UIAbility instance corresponds to a mission displayed in the recent task list.
Every mission retains a snapshot of the UIAbility instance. After the UIAbility instance is destroyed, the mission information (including the ability information and mission snapshot) is retained until the mission is deleted.
NOTE
The specified mode is supported in the stage model only.
你可能感兴趣的鸿蒙文章
openharmony 鸿蒙 create-pageability
openharmony 鸿蒙 lifecycleform-switch
openharmony 鸿蒙 bind-serviceability-from-stage
openharmony 鸿蒙 lifecycleservice-switch
openharmony 鸿蒙 pageability-launch-type
openharmony 鸿蒙 pageability-overview
openharmony 鸿蒙 uiserviceextension-sys
openharmony 鸿蒙 uiability-launch-type