Bundle Error Codes

NOTE

This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.

17700001 Bundle Name Does Not Exist

Error Message

The specified bundle name is not found.

Description

When a query API is called, the bundle name passed in does not exist.

Possible Causes

  1. The bundle name is misspelled.
  2. The corresponding bundle is not installed.

Solution

  1. Check whether the spelling of the bundle name is correct.
  2. Check whether the corresponding bundle is installed.

17700002 Module Name Does Not Exist

Error Message

The specified module name is not found.

Description

When a query API or an installation-free API is called, the module name passed in does not exist.

Possible Causes

  1. The module name is misspelled.
  2. The module is not installed.

Solution

  1. Check whether the spelling of the module name is correct.
  2. Check whether the module is installed.

17700003 Ability Name Does Not Exist

Error Message

The specified ability name is not found.

Description

When a query API is called, the ability name passed in does not exist.

Possible Causes

  1. The ability name is misspelled.
  2. The application does not have the ability specified by abilityName.

Solution

  1. Check whether the spelling of the ability name is correct.
  2. Check whether the application has the ability specified by abilityName.

17700004 User ID Does Not Exist

Error Message

The specified user ID is not found.

Description

When a user-related API is called, the user ID passed in does not exist.

Possible Causes

  1. Incorrect username.
  2. The user does not exist in the system.

Solution

  1. Check whether the user ID is correct.
  2. Check whether the user exists.

17700005 appId Is an Empty String

Error Message

The specified app ID is empty string.

Description

When an API of the appControl module is called, the application ID passed in does not exist.

Possible Causes

appId is an empty string.

Solution

Check whether appId is an empty string.

17700006 Permission Does Not Exist

Error Message

The specified permission is not found.

Description

When the getPermissionDef API of the bundleManager module is called, the permission passed in does not exist.

Possible Causes

  1. The permission name is misspelled.
  2. The permission does not exist.

Solution

  1. Check whether the spelling of the permission name is correct.
  2. Check whether the permission exists.

17700007 Incorrect Device ID

Error Message

The specified device ID is not found.

Description

When an API of the distributedBundle module is called, the device ID passed in does not exist.

Possible Causes

  1. The device ID is incorrect.
  2. The device ID does not exist.

Solution

  1. Check whether the device ID is correct.
  2. Check whether the device ID exists.

17700010 Bundle Installation Failure Due to File Parsing Failure

Error Message

Failed to install the HAP because the HAP fails to be parsed.

Description

When the install API of the installer module is called, the HAP passed in fails to be parsed.

Possible Causes

  1. The HAP is not in ZIP format.
  2. The configuration file in the HAP is not in JSON format.
  3. Necessary fields are missing in the configuration file.

Solution

  1. Check whether the HAP is in ZIP format.
  2. Check whether the configuration file is in JSON format.
  3. Check whether an error message is displayed when DevEco Studio compiles the HAP. If necessary fields are missing, an error message will be displayed.

17700011 Bundle Installation Failure Due to Signature Verification Failure

Error Message

Failed to install the HAP because the HAP signature fails to be verified.

Description

Calling the install API of the installer module to install the bundle fails due to signature verification failure.

Possible Causes

  1. The HAP is not signed.
  2. The source of the HAP signature information is unreliable.
  3. The signature information of the HAP used for an upgrade is different from that of the installed HAP.
  4. The signature information of multiple HAPs is inconsistent.

Solution

  1. Check whether the HAP is signed.
  2. Ensure that the signing certificate of the HAP is applied for from the application market.
  3. Check whether the same certificate is used for signing multiple HAPs.
  4. Check whether the certificate used for signing the upgrade HAP is the same as the certificate used for signing the installed HAP.

17700012 Bundle Installation Failure Due to Invalid File Path or Too Large File

Error Message

Failed to install the HAP because the HAP path is invalid or the HAP is too large.

Description

Calling the install API of the installer module to install the bundle fails because the HAP path is invalid or the HAP is too large.

Possible Causes

  1. The path of the HAP does not exist.
  2. The path of the HAP is inaccessible.
  3. The size of the HAP exceeds the upper limit 4 GB.

Solution

  1. Check whether the HAP path exists.
  2. Check whether the HAP is read only or executable.
  3. Check whether the size of the HAP exceeds 4 GB.

17700015 Bundle Installation Failure Due to Different Configuration Information of Multiple HAPs

Error Message

Failed to install the HAPs because they have different configuration information.

Description

Calling the install API of the installer module to install the bundle fails because the HAPs have different configuration information.

Possible Causes

The fields under app in the configuration files of these HAPs are inconsistent.

Solution

Check whether the fields under app are the same.

17700016 Bundle Installation Failure Due to Insufficient System Disk Space

Error Message

Failed to install the HAP because of insufficient system disk space.

Description

Calling the install API of the installer module to install the bundle fails due to insufficient system disk space.

Possible Causes

The system disk space is insufficient.

Solution

Check whether the system has sufficient disk space.

17700017 Bundle Installation Failure Because the Version to Install is Too Earlier

Error Message

Failed to install the HAP since the version of the HAP to install is too early.

Description

Calling the install API of the installer module to install the bundle fails because the version to install is earlier than the version in use.

Possible Causes

The version number is earlier than the version in use.

Solution

Ensure that the version of the bundle to install is not earlier than the version in use.

17700018 Bundle Installation Failure Becase the Dependent Module Does Not Exist

Error Message

Failed to install because the dependent module does not exist.

Description

The dependent module does not exist during the HAP or HPS installation.

Possible Causes

The dependent module is not installed.

Solution

Install the dependent modules first.

17700020 Failure to Uninstall Preinstalled Applications

Error Message

The preinstalled app cannot be uninstalled.

Description

Calling the uninstall API of the installer module to uninstall a preinstalled application fails.

Possible Causes

  1. You might want to uninstall a non-preinstalled application but passed the bundle name of a preinstalled app.
  2. The preinstalled application cannot be uninstalled.

Solution

  1. Check whether the bundle name is correct.
  2. Check whether the preinstalled application can be uninstalled.

17700021 Invalid UID

Error Message

The specified uid is invalid.

Description

When the getBundleNameByUid API of the bundleManager module is called, the UID passed in is invalid.

Possible Causes

  1. The UID is misspelled.
  2. The UID does not exist.

Solution

  1. Check whether the UID is correct.
  2. Check whether the UID exists.

17700022 Invalid Source File

Error Message

The input source file is invalid.

Description

When the getBundleArchiveInfo API of the bundleManager module is called, the HAP path passed in is invalid.

Possible Causes

  1. The source file to be parsed does not exist.
  2. The source file to be parsed is not in ZIP format.

Solution

  1. Check whether the source file to be parsed exists.
  2. Check whether the source file to be parsed is in ZIP format.

17700023 Default Application Does Not Exist

Error Message

The specified default app does not exist.

Description

When the getDefaultApplication API of the defaultAppManager module is called, the specified default application does not exist.

Possible Causes

No default application is set for the device.

Solution

Check whether the default application is set on the device.

17700024 Configuration File Does Not Exist

Error Message

Failed to get the profile because there is no profile in the HAP.

Description

When an API for querying the profile is called, the configuration file does not exist

Possible Causes

  1. The metadata name passed in the API does not exist in the configuration file.
  2. The content of the configuration file is not in JSON format.

Solution

  1. Check whether the metadata name in the ability or extensionAbility to be queried exists.
  2. Check whether the content of the profile to be queried is in JSON format.

17700025 Invalid Type

Error Message

The specified type is invalid.

Description

When an API of the defaultAppManager module is called, the type passed in is invalid.

Possible Causes

  1. The type passed in the API is misspelled.
  2. The type passed in the API does not exist.

Solution

  1. Check whether the spelling of type is correct.
  2. Enter a type that exists.

17700026 Bundle Disabled

Error Message

The specified bundle is disabled.

Description

When an API for querying bundle information is called, the specified bundle is disabled.

Possible Causes

The bundle on the device has been disabled and cannot be queried.

Solution

Check whether the bundle on the device is disabled.

17700027 Distributed Service Is Not Started

Error Message

The distributed service is not running.

Description

When an API of the distributedBundle module is called, the distributed service is not started.

Possible Causes

The device is not networked.

Solution

Check whether the device is networked.

17700028 Mismatch Between Ability and Type

Error Message

The ability does not match the type.

Description

When the setDefaultApplication API of the defaultAppManager module is called, the ability and type passed in do not match.

Possible Causes

The ability and type are misspelled.

Solution

Check whether the spellings of ability and type are correct.

17700029 Disabled Ability

Error Message

The specified ability is disabled.

Description

When an API for querying ability information is called, the specified ability is disabled.

Possible Causes

The specified ability is disabled.

Solution

Check whether the ability is disabled. You can run the bm commands to query the information.

17700030 Failure in Clearing Cache Files

Error Message

The specified bundle does not support clearing of cache files.

Description

When the cleanBundleCacheFiles API of the bundleManager module is called, the specified bundle does not support cache file clearing.

Possible Causes

The application is a system application and the AllowAppDataNotCleared field is configured in the signing certificate.

Solution

  1. Check whether the application is a system application. You can run the bm commands to query the application information and check whether the value of isSystemApp is true.
  2. Check whether the AllowAppDataNotCleared field is configured for the application. You can run the bm commands to query the application information and check whether the value of userDataClearable is true.