Bundle Manager Subsystem Changelog

cl.bundlemanager.1 Bottom-Layer Capability Changed So That Only the System Resource HAP Supports Custom Permissions

Only the system resource HAP supports custom permissions. During HAP parsing, the bundle manager module parses the definePermissions field only in the configuration file of the resource HAP (bundle name: ohos.global.systemres), but not this field in other HAPs. This field is used to define permissions. If an application requires custom permissions, add the permissions under the definePermissions field in the configuration file of the system resource HAP. For details about the permission format, see Defining Permissions.

Change Impact
After an upgrade to the new version image, the custom permission of the application does not take effect, and the authorization fails.

Key API/Component Changes
The bottom-layer capability of the bundle manager module is changed. Only the system resource HAP supports custom permissions.

Adaptation Guide
If an application requires custom permissions, add the permissions under the definePermissions field in the configuration file of the system resource HAP. For details about the permission format, see Defining Permissions.

cl.bundlemanager.2 Level-2 Module File Names Changed

The level-2 module file names of the bundle manager module are changed to their respective API names in the file, as listed below.

To sum up, except packInfo, which is changed to BundlePackInfo, the other file names are changed to start with uppercase letters.

Change Impact
The change of the level-2 module file names does not affect the use of the level-1 module. If a level-2 module interface under bundleManager is directly imported to the .ts file and an error is reported during compilation on DevEco Studio, you must change the name of the imported file.

Key API/Component Changes
The .d.ts file names in the bundleManager folder are changed to their respective API names in the file.

Adaptation Guide
Generally, no adaptation is required. If a file in the bundleManager folder is directly imported to the application, you must change the imported file name as follows:

Before change:

import {AbilityInfo} from 'bundleManger/abilityInfo';
import {ExtensionAbilityInfo} from 'bundleManger/extensionAbilityInfo';
import {BundlePackInfo} from 'bundleManger/packInfo';

After change:

import {AbilityInfo} from 'bundleManger/AbilityInfo';
import {ExtensionAbilityInfo} from 'bundleManger/ExtensionAbilityInfo';
import {BundlePackInfo} from 'bundleManger/BundlePackInfo';

cl.bundlemanager.3 LaunchType Enum Type Name Changed from STANDARD to MULTITON

The enum type name of LaunchType is changed from STANDARD to MULTITON. The enum value remains unchanged, indicating the multi-instance type.

Change Impact
The LaunchType.STANDARD type does not take effect.

Key API/Component Changes
The enum type name of LaunchType is changed from STANDARD to MULTITON.

Adaptation Guide
Change LaunchType.STANDARD to LaunchType.MULTITON for your application.

cl.bundlemanager.4 Changed the isVisible Field in the AbilityInfo Struct to exported

The isVisible field in the AbilityInfo struct is changed to exported. The type remains unchanged, indicating whether the ability can be exported and used by other abilities.

Change Impact
The isVisible field does not take effect.

Key API/Component Changes
The isVisible field in the AbilityInfo struct is changed to exported, and the type remains unchanged.

Adaptation Guide
Change isVisible to exported for your application.

cl.bundlemanager.5 Changed the isVisible Field in the ExtensionAbilityInfo Struct to exported

The isVisible field in the ExtensionAbilityInfo struct is changed to exported. The type remains unchanged, indicating whether the ability can be exported and used by other abilities.

Change Impact
The isVisible field does not take effect.

Key API/Component Changes
The isVisible field in the ExtensionAbilityInfo struct is changed to exported, and the type remains unchanged.

Adaptation Guide
Change isVisible to exported for your application.

cl.bundlemanager.6 Changed the visible Field in the ModuleAbilityInfo Struct to exported

The visible field in the ModuleAbilityInfo struct is changed to exported. The type remains unchanged, indicating whether the ability can be exported and used by other abilities.

Change Impact
The visible field does not take effect.

Key API/Component Changes
The visible field in the ModuleAbilityInfo struct is changed to exported, and the type remains unchanged.

Adaptation Guide
Change visible to exported for your application.

你可能感兴趣的鸿蒙文章

harmony 鸿蒙1.0.0 （2022/03/09）

harmony 鸿蒙1.0.0 (2022/03/09)

harmony 鸿蒙OpenHarmony Docker镜像

harmony 鸿蒙OpenHarmony Docker Image

harmony 鸿蒙Legal Notices

harmony 鸿蒙OpenHarmony Project

harmony 鸿蒙IDL Specifications and User Guide (for System Applications Only)

harmony 鸿蒙Application Development

harmony 鸿蒙OAID Service

harmony 鸿蒙AI