提交 087ff296 编写于 作者: G Gloria

Update docs against 22098+22080+22149

Signed-off-by: wusongqing<wusongqing@huawei.com>
上级 41d6c63c
...@@ -784,3 +784,59 @@ During application installation, the code signature file of the installation pac ...@@ -784,3 +784,59 @@ During application installation, the code signature file of the installation pac
1. Ensure that the module corresponding to the code signature file is contained in the installation package. 1. Ensure that the module corresponding to the code signature file is contained in the installation package.
2. Provide a valid path of the code signature file. 2. Provide a valid path of the code signature file.
3. Use the code signature file that matches the installation package. 3. Use the code signature file that matches the installation package.
## 17700049 Update Failure Because of Incorrect Bundle Name
**Error Message**
Failed to install the HAP because the bundleName is different from the bundleName of the caller application.
**Description**
During the update of an enterprise MDM application, the bundleName passed in is different from that of the caller.
**Possible Causes**
The HAP or HSP to be installed does not belong to the current application.
**Solution**
Ensure that the HAP or HSP to be installed belongs to the current application.
## 17700050 Enterprise Device Verification Failure
**Error Message**
Failed to install the HAP because enterprise normal/MDM bundle cannot be installed on non-enterprise device.
**Description**
Users try to install an enterprise Normal or MDM application on a non-enterprise device.
**Possible Causes**
The device is not an enterprise device.
**Solution**
1. Use an enterprise device.
2. Ensure that **const.bms.allowenterprisebundle** is set to **true**.
## 17700051 Update Failure Because of Incorrect Distribution Type
**Error Message**
Failed to install the HAP because the distribution type of caller application is not enterprise_mdm.
**Description**
During the update of an enterprise MDM application, the distribution type of the caller is not enterprise MDM.
**Possible Causes**
The distribution type of the caller is not enterprise MDM.
**Solution**
Ensure that the signature file of the application is correctly configured.
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册