Huawei third-party channel integration

Preparations

• You have integrated the Mobile Push SDK. For more information, see Android SDK integration.

• You have registered an application on HUAWEI Developers. If you have not, log on to HUAWEI Developers to register your application. Then, obtain the App ID and Client Secret from your application details.

  

• You have configured the SHA256 certificate fingerprint on HUAWEI Developers. If you have not, see the official Huawei document Configure in AppGallery Connect.

• You have set up message receipts. If you have not, see Message Receipt.

  Important

  If you use the assistive pop-up window, arrival rate statistics for the Huawei channel only include notifications that users click. Notifications that are not clicked are excluded from the statistics. To help Mobile Push collect more comprehensive push data, set up message receipts on the Huawei side.

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

  If you configure multiple webhook addresses, you must set this address as the default receipt. Alternatively, you can configure the receipt ID in the Default Receipt ID field in the console.

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

  Note

  The AppSecret required to configure Huawei push parameters in the EMAS console is the Client Secret from your application information on HUAWEI Developers.

Step 1: Add the SDK to your application

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

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

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

Step 2: Configure and use the SDK

<meta-data
	android:name="com.huawei.hms.client.appid"
 	android:value="appid=YOUR_HUAWEI_APP_ID" />

// The registration method automatically skips registration if Huawei Push Kit is not supported.
HuaWeiRegister.register(application)

// The registration method automatically skips registration if Huawei Push Kit is not supported.
HuaWeiRegister.register(application);

# Huawei channel
-keep class com.huawei.** {*;}
-dontwarn com.huawei.**

Step 3: Verify the integration

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

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

What to do next

You can now push notifications to the notification bar on mobile devices through the third-party channel from the EMAS console. However, to process the logic after a notification is clicked, you must use the assistive pop-up window to receive push data. For more information, see Integrate the assistive pop-up window.

Third-party channel FAQ

• Error 6003 is returned during Huawei channel registration: The certificate fingerprint configuration does not match. Perform the Huawei third-party channel integration steps again.

• Troubleshoot third-party channel and pop-up window issues on Android

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

• The corresponding Activity fails to open after a notification from a third-party channel is clicked on Android

• An error that indicates a body parsing failure is reported when the assistive pop-up window starts on Android

• "register not in main process, return" is displayed after the Mobile Push third-party channel is integrated