Application Package FAQ

Note:

Currently in the beta phase.

How to Obtain Fingerprint Information from Signature

1. Obtain via API call.

   You can call bundleManager.getBundleInfoForSelf to retrieve your own BundleInfo, which contains signatureInfo. The signatureInfo includes fingerprint information.

   import ohos.base.*
   import kit.AbilityKit.*
   import ohos.business_exception.BusinessException
   import ohos.hilog.Hilog
   
   let bundleFlags =  GET_BUNDLE_INFO_WITH_APPLICATION.getValue() | GET_BUNDLE_INFO_WITH_SIGNATURE.getValue()
   try {
       let res = BundleManager.getBundleInfoForSelf(bundleFlags)
       let fingerprint = res.signatureInfo.fingerprint
       Hilog.info(1, "1", "info", "getBundleInfoForSelf successfully, fingerprint: ${fingerprint}")
   } catch (e: BusinessException)  {
       Hilog.error(1, "1", "info", "Failed to getBundleInfoForSelf. Code is ${e.code}, message is ${e.message}")
   }
   

2. Obtain fingerprint information via the bm tool.

   hdc shell
   # Replace com.example.myapplication with the actual package name
   bm dump -n com.example.myapplication | grep fingerprint
   

   

3. Obtain via .cer certificate file. Refer to APP Filing FAQ for how to obtain public key and signature information for OpenHarmony applications/services.

4. Obtain via keytool. For details, refer to Generating Signature Certificate Fingerprint.

What is appIdentifier

appIdentifier is a field in the Profile Signature File, serving as the unique identifier for an application. It is generated during application signing, where:

1. When generated via DevEco Studio's Auto-Signing, the appIdentifier field is randomly generated. Signing on different devices or re-signing will result in different appIdentifier values.

2. For manual signing configuration, refer to [Application Package Signing Tool Guide](https://gitcode.com/openharmony/docs/blob/master/en/application-dev/security/hapsigntool-guidelines.md). In this case, the appIdentifier field takes the value from the app-identifier field in the [HarmonyAppProvision Configuration File](https://gitcode.com/openharmony/docs/blob/master/en/application-dev/security/app-provision-structure.md).

Therefore, for scenarios requiring consistent appIdentifier across devices (e.g., cross-device debugging, cross-application interaction debugging, or multi-user collaborative development with shared keys), manual signing is recommended. For specific scenarios, refer to Usage Scenario Description.

How to Obtain appIdentifier from Application Information

1. Call bundleManager.getBundleInfoForSelf to retrieve your own BundleInfo, which contains signatureInfo. The signatureInfo includes appIdentifier information.

   import ohos.base.*
   import kit.AbilityKit.*
   import ohos.business_exception.BusinessException
   import ohos.hilog.Hilog
   
   let bundleFlags =  GET_BUNDLE_INFO_WITH_APPLICATION.getValue() | GET_BUNDLE_INFO_WITH_SIGNATURE.getValue()
   try {
       let res = BundleManager.getBundleInfoForSelf(bundleFlags)
       let appIdentifier = res.signatureInfo.appIdentifier
       Hilog.info(1, "1", "info", "getBundleInfoForSelf successfully, appIdentifier: ${appIdentifier}")
   } catch (e: BusinessException)  {
       Hilog.error(1, "1", "info", "Failed to getBundleInfoForSelf. Code is ${e.code}, message is ${e.message}")
   }
   

2. Obtain via the bm tool.

   hdc shell
   # Replace com.example.myapplication with the actual package name
   bm dump -n com.example.myapplication | grep appIdentifier