1# BundleInfo 2<!--Kit: Ability Kit--> 3<!--Subsystem: BundleManager--> 4<!--Owner: @wanghang904--> 5<!--Designer: @hanfeng6--> 6<!--Tester: @kongjing2--> 7<!--Adviser: @Brilliantry_Rui--> 8 9The module defines the bundle information. An application can obtain its own bundle information through [bundleManager.getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself), with [bundleFlags](js-apis-bundleManager.md#bundleflag) set to the information to be contained in the returned [BundleInfo](js-apis-bundleManager-bundleInfo.md). 10 11> **NOTE** 12> 13> The initial APIs of this module are supported since API version 9. Newly added APIs will be marked with a superscript to indicate their earliest API version. 14 15## Modules to Import 16 17```ts 18import { bundleManager } from '@kit.AbilityKit'; 19``` 20 21## BundleInfo 22 23**System capability**: SystemCapability.BundleManager.BundleFramework.Core 24 25| Name | Type | Read-Only| Optional| Description | 26| --------------------------------- | ------------------------------------------------------------ | ---- | ---- | ------------------------------------------------------------ | 27| name | string | Yes | No | Name of the application package. It corresponds to the **bundleName** field in the [app.json5](../../quick-start/app-configuration-file.md) file.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 28| vendor | string | Yes | No | Vendor of the application package. It corresponds to the **vendor** field in the [app.json5](../../quick-start/app-configuration-file.md) file.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 29| versionCode | number | Yes | No | Version code of the application package. It corresponds to the **versionCode** field in the [app.json5](../../quick-start/app-configuration-file.md) file.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 30| versionName | string | Yes | No | Version description of the application package. It corresponds to the **versionName** field in the [app.json5](../../quick-start/app-configuration-file.md) file.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 31| minCompatibleVersionCode | number | Yes | No | Minimum compatible version of the application package in the distributed scenario. It corresponds to the **minCompatibleVersionCode** field in the [app.json5](../../quick-start/app-configuration-file.md) file.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 32| targetVersion | number | Yes | No | Target version of the application. It corresponds to the **targetAPIVersion** field in the [app.json5](../../quick-start/app-configuration-file.md) file.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 33| appInfo | [ApplicationInfo](js-apis-bundleManager-applicationInfo.md) | Yes | No | Application information. The information can be obtained by passing in **GET_BUNDLE_INFO_WITH_APPLICATION** to the **bundleFlags** parameter of [getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself).<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 34| hapModulesInfo | Array\<[HapModuleInfo](js-apis-bundleManager-hapModuleInfo.md)> | Yes | No | Module configuration information. The information can be obtained by passing in **GET_BUNDLE_INFO_WITH_HAP_MODULE** to the **bundleFlags** parameter of [getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself).<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 35| reqPermissionDetails | Array\<[ReqPermissionDetail](#reqpermissiondetail)> | Yes | No | Detailed information of the permissions to request from the system. The information can be obtained by passing in **GET_BUNDLE_INFO_WITH_REQUESTED_PERMISSION** to the **bundleFlags** parameter of [getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself).<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 36| permissionGrantStates | Array\<[bundleManager.PermissionGrantState](js-apis-bundleManager.md#permissiongrantstate)> | Yes | No | Permission grant state. The information can be obtained by passing in **GET_BUNDLE_INFO_WITH_REQUESTED_PERMISSION** to the **bundleFlags** parameter of [getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself).<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 37| signatureInfo | [SignatureInfo](#signatureinfo) | Yes | No | Signature information of the bundle. The information can be obtained by passing in **GET_BUNDLE_INFO_WITH_SIGNATURE_INFO** to the **bundleFlags** parameter of [getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself).<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 38| installTime | number | Yes | No | Timestamp for the installation of the application package. It measures the milliseconds that have passed since the Unix epoch (January 1, 1970, 08:00:00 UTC+8), in milliseconds.<br>**Atomic service API**: This API can be used in atomic services since API version 11.<br> **NOTE**<br> If the current time is not obtained when the device is powered on for the first time from the factory, the Unix epoch (1970-01-01 08:00:00 UTC+8) is used as the start time of the current system. For example, if the time is not obtained after startup and the installation succeeds after a 32-second wait, the application package installation timestamp is 32000.| 39| updateTime | number | Yes | No | Timestamp for the last update of the application package. It measures the milliseconds that have passed since the Unix epoch (January 1, 1970, 08:00:00 UTC+8), in milliseconds.<br>**Atomic service API**: This API can be used in atomic services since API version 11.| 40| routerMap<sup>12+</sup> | Array\<[RouterItem](js-apis-bundleManager-hapModuleInfo.md#routeritem12)> | Yes | No | Router table of the application. The table is obtained by deduplicating and combining the **routerMap** information under **hapModulesInfo** based on the **name** field in **RouterItem**. The information can be obtained by passing in **GET_BUNDLE_INFO_WITH_HAP_MODULE** and **GET_BUNDLE_INFO_WITH_ROUTER_MAP** to the **bundleFlags** parameter of [getBundleInfoForSelf](js-apis-bundleManager.md#bundlemanagergetbundleinfoforself).<br>**Atomic service API**: This API can be used in atomic services since API version 12.| 41| appIndex<sup>12+</sup> | number | Yes | No | Index of an application clone. It takes effect only for application clones.| 42| firstInstallTime<sup>18+</sup> | number | Yes | Yes | Timestamp for the initial installation of the application package. It measures the milliseconds that have passed since the Unix epoch (January 1, 1970, 08:00:00 UTC+8), in milliseconds. For preinstalled applications, the initial installation timestamp is 1533657660000.<br>**Atomic service API**: This API can be used in atomic services since API version 18.| 43 44 45## ReqPermissionDetail 46 47Provides the detailed information of the permissions to request from the system. 48> **NOTE** 49> 50> If multiple packages of an application have requested the same permission but with different reasons, the system returns only one reason based on a descending priority order: entry HAP > feature HAP > in-app HSP. 51 52**Atomic service API**: This API can be used in atomic services since API version 11. 53 54**System capability**: SystemCapability.BundleManager.BundleFramework.Core 55 56| Name | Type | Read-Only| Optional| Description | 57| --------------------- | ----------------------- | ---- | ---- | ---------------------| 58| name | string | No | No | [Name of the permission](../../security/AccessToken/app-permissions.md) to request. | 59| moduleName<sup>10+</sup> | string | No | No | Name of the module that requests the permission. | 60| reason | string | No | No | Reason for requesting the permission. | 61| reasonId | number | No | No | ID of the reason for requesting the permission.| 62| usedScene | [UsedScene](#usedscene) | No | No | Use scenario and timing for using the permission.| 63 64 65 66## UsedScene 67 68Describes the use scenario and timing for using the permission. 69 70**Atomic service API**: This API can be used in atomic services since API version 11. 71 72**System capability**: SystemCapability.BundleManager.BundleFramework.Core 73 74| Name | Type | Read-Only| Optional| Description | 75| --------- | -------------- | ---- | ---- | --------------------------- | 76| abilities | Array\<string> | No | No | Abilities that use the permission. | 77| when | string | No | No | Time when the permission is used. The value can be **inuse** or **always**. | 78 79## SignatureInfo 80 81Describes the signature information of the bundle. 82 83**System capability**: SystemCapability.BundleManager.BundleFramework.Core 84 85| Name | Type | Read-Only| Optional| Description | 86| --------- | -------------- | ---- | ---- | --------------------------- | 87| appId | string | Yes | No | appId of the application. It is composed of the bundle name, an underscore, and the Base64-encoded certificate public key.<br>**Atomic service API**: This API can be used in atomic services since API version 11. | 88|fingerprint| string | Yes | No | Fingerprint information of the application package. It is generated by calculating the hash value of the signing certificate using the SHA-256 algorithm. This field changes when the used signing certificate changes.<br>**Atomic service API**: This API can be used in atomic services since API version 11. | 89|appIdentifier<sup>11+</sup>| string | Yes | No | Unique ID of the application. It is the [app ID](https://developer.huawei.com/consumer/en/doc/app/agc-help-createharmonyapp-0000001945392297), which is a random string, allocated by AppGallery Connect during the creation of the application. This ID does not change along the application lifecycle, including version updates, certificate changes, public and private key changes, and application transfers. Manual signing is mandatory for cross-device debugging and cross-application interaction debugging. For details about how to select a signing mode, see [Use Cases for Automatic and Manual Signing](https://developer.huawei.com/consumer/en/doc/harmonyos-guides/ide-signing#section54361623194519).<br>**Atomic service API**: This API can be used in atomic services since API version 11. | 90|certificate<sup>14+</sup>| string | Yes | Yes | Public key of the application certificate.<br>**Atomic service API**: This API can be used in atomic services since API version 14. | 91 92## AppCloneIdentity<sup>14+<sup> 93 94Describes the identity information of an application clone. 95 96**System capability**: SystemCapability.BundleManager.BundleFramework.Core 97 98| Name | Type | Read-Only| Optional| Description | 99| --------- | -------------- | ---- | ---- | --------------------------- | 100| bundleName | string | Yes | No | Bundle name of the application. | 101| appIndex | number | Yes | No | Index of the application clone.| 102