Consistency Verification for Application Installation and Update

As applications become more and more complex, they are split into multiple modules for development and maintenance. Different teams are responsible for one or more modules. During application installation and update, consistency verification is performed on different fields to ensure application security and validity. This topic describes the consistency verification rules for signing certificates and configuration files during multi-module installation or update.

NOTE

If the values of the versionCode field in the app.json5 configuration file are the same, the installed or updated packages are of the same version.

During application packaging, validity verification is performed. For details, see Packing Tool.

Consistency Verification for Signing Certificate

Field	Description	Consistency Verification for Installations	Consistency Verification for Updates
appId	Application ID, which is a unique identifier of the application. For details, see What Is appId.	Yes	Either appId or appIdentifier is the same.
appIdentifier	Unique ID of the application. For details, see What Is appIdentifier.	Yes	Either appId or appIdentifier is the same.
appDistributionType	Application distribution type specified in app-distribution-type of the application profile.	Yes	No consistency verification is performed when an application is updated to a later version.
appProvisionType	Profile type. The value comes from type defined in the application profile. Profiles are classified into two types: debug profiles are used for local debugging and release profiles are used for application release.	Yes	No consistency verification is performed when an application is updated to a later version.
apl	Application APLs, which are classified into three levels: normal, system_basic, and system_core.	Yes	No consistency verification is performed when an application is updated to a later version.

Consistency Verification for Configuration File

Field	Description	Consistency Verification for Installations	Consistency Verification for Updates
bundleName	Bundle name. This field comes from the app.json5 configuration file.	Yes	Yes
versionCode	Version code of the application. This field comes from the app.json5 configuration file.	Yes	Yes
apiReleaseType	Release type of the SDK used to run an application. An uninstalled application contains multiple module packages. When the modules are installed one by one, consistency verification is not performed. This field comes from the app.json5 configuration file.	No	Yes
singleton	Whether an application is installed for a single user (User 0).	No	Yes
appType	Application type, which specifies the third-party application or system application.	Yes	Yes
isStage	Whether an application is in the stage model.	Yes. The FA model and stage model cannot be changed in the same version.	No
targetBundleName	Target bundle name. The application with this field has the overlay feature. This field comes from the app.json5 configuration file.	Yes	Yes
targetPriority	Priority of the target application. This field comes from the app.json5 configuration file.	Yes	Yes
bundleType	Bundle type. This field comes from the app.json5 configuration file.	Yes	Yes
installationFree	Whether installation-free is supported. This field comes from the module.json5 configuration file.	Yes	Yes
debug	Whether the application can be debugged. This field comes from the app.json5 configuration file.	Yes	No
moduleType	Module type. This field comes from the type field in the module.json5 configuration file.	Yes. In the same version, the module name of the entry type cannot be modified.	Yes