Honor channel integration

Prerequisites

• You have integrated the Mobile Push SDK as described in Android SDK Integration.

• You have registered an application on HONOR Developers. If you have not done so, log on to HONOR Developers to register your application. You can obtain the App ID, Client ID, and Client Secret from Application Services > Push Service > View Application.

• You have configured a signing certificate fingerprint on the HONOR Developers platform. If you have not done so, see the official Honor document Certificate Fingerprint Generation Guide.

• You have set up message receipts. If you have not done so, see Message receipts for instructions.

  Important

  When you use the auxiliary pop-up window, the delivery rate statistics for the Honor channel include only scenarios where users click the push notifications in the Honor pop-up window. Scenarios where users do not click the notifications are not included. You can set up message receipts on the Honor platform to help Mobile Push better collect push data.

  To enable receipts, configure the webhook address: https://amspush-ack.aliyuncs.com/ho/.

• You have configured the Honor push key (App ID) in the EMAS console. If you have not done so, log on to the EMAS Mobile Push console and set your Honor push key (App ID). For more information, see Configure third-party channel keys.

Step 1: Add the SDK to your application

dependencyResolutionManagement {
  repositories {
    maven {
      url 'https://developer.hihonor.com/repo'
    }
  }
}

allprojects {
  repositories {
    maven {
      url 'https://developer.hihonor.com/repo'
    }
  }
}

dependencies {
    implementation 'com.aliyun.ams:alicloud-android-third-push:x.x.x'
    implementation 'com.aliyun.ams:alicloud-android-third-push-honor:x.x.x'
}

Step 2: Configure and use the SDK

1. Configure the AppID

In the AndroidManifest.xml file of your application, add metadata under the application node to configure the AppID.

<meta-data
	android:name="com.hihonor.push.app_id"
	android:value="Your Honor AppID" />

2. Initialize the SDK

Initialize the SDK as follows:

// The registration method automatically checks if the device supports Honor push. If not, the registration is skipped.
HonorRegister.register(application)

// The registration method automatically checks if the device supports Honor push. If not, the registration is skipped.
HonorRegister.register(application);

3. Configure obfuscation

If code obfuscation is enabled in a project that integrates the push SDK, you must add the following ProGuard configuration for the vendor channel.

# Honor channel
-ignorewarnings
-keepattributes *Annotation*
-keepattributes Exceptions
-keepattributes InnerClasses
-keepattributes Signature
-keepattributes SourceFile,LineNumberTable
-keep class com.hihonor.push.**{*;}

Step 3: Verify the integration

1. Enable SDK logs

val pushService = PushServiceFactory.getCloudPushService()
// This line is for debug packages only and is not required for release packages.
pushService.setLogLevel(CloudPushService.LOG_DEBUG)

CloudPushService pushService = PushServiceFactory.getCloudPushService();
// This line is for debug packages only and is not required for release packages.
pushService.setLogLevel(CloudPushService.LOG_DEBUG);      

2 Confirmation method

To check whether the Honor channel is registered successfully, filter the logs for the MPS:HonorRegister keyword. If no logs related to getToken failure appear, the registration was successful.

What to do next

You can now use the EMAS console to send push notifications to the notification bar on mobile devices through the Honor channel. However, to handle the logic after a user clicks a notification, you must use an auxiliary pop-up window to receive push data. For more information, see Integrate an auxiliary pop-up window.

Third-party channel FAQ

• Troubleshoot issues with third-party channels and pop-up windows on Android

• Conflicts between the Android third-party channel SDK and other third-party SDKs

• Unable to open the corresponding activity after clicking a notification from a third-party channel on Android

• Troubleshoot body parsing errors when the auxiliary pop-up window starts on Android

• The "register not in main process, return" error occurs after you integrate the Mobile Push third-party channel