1. Description of the problem:
Currently Huawei push API uses v2 or v1 version, may I ask if the latest hongmengnext currently using v3 version is compatible with v2 or v1, and in turn will the v2 or v1 api be able to push hongmengnext devices?
Solution:
The v3 interface is compatible with pushing to non-HarmonyOS NEXT devices, and older versions of the interface are not compatible with pushing to HarmonyOS NEXT devices.
2. Description of the problem:
gainPush Tokenreport an error Get push token catch error: 1000900010 Illegal application identity.
Solution:
Check that the following configuration items are correct:
1. Make sure that the fingerprint of the application signing certificate configured on AppGallery Connect is the same as the actual certificate of the application, and that the application with API 9 or above needs to choose the "Add Public Key Fingerprint (HarmonyOS API 9 and above)" method of configuration.
/consumer/cn/doc/app/agc-help-signature-info-0000001628566748#section5181019153511
2. Configure client_id in src/main/module.json5 (e.g. entry/src/main/module.json5) under the module level of the project, you need to use the Client_id in the Project Settings->General Page->Applications->OAuth 2.0 Client ID (Credentials) ID in the OAuth 2.0 client ID (credentials).
/consumer/cn/doc/harmonyos-guides/push-preparations-0000001727885250#section792641732919
Note: It takes some time to take effect after configuring the certificate fingerprint, so it is recommended to retry after 30-60 minutes.
3. Description of the problem:
-
Does a normal message with push-type=0 with an image have to be tuned for the image windup interface first?
-
What is the maximum expiration time of the expireTime returned by the image wind control interface?
Solution:
1, the current send push-type: 0 notification message does not limit the picture must be wind control, the picture meets the specifications of the document description can be.
/consumer/cn/doc/harmonyos-guides-V5/push-send-alert-0000001862404293-V5#section62011739001
2、expireTime Generally 7 days.
4. Description of the problem:
The application has applied for a debug certificate in AppGallery Connect, enabled the push service, configured the debug certificate signature in the app project, and configured the client_id in the application, but it fails to get the token and reports an error message get token fail:, {:Error, :Illegal application identity.} ,json:{"code":1000900010}}
Solution:
1, in the API management, open the API of the relevant service. there will be a certain delay, usually about 10 minutes.
2, The HarmonyOS app type was not selected when the app was created on AppGallery Connect.
3, module.json5 file in the metadata node under the clientid written correctly. You need to write the client_id information directly, you can't refer to the value in the resource file through the $ character, you can't resolve this kind of reference currently.
4, the signing certificate uses this option in the Configuration method "Select SHA256 public key fingerprint''.
a. Generate configuration fingerprints:/consumer/cn/doc/harmonyos-guides/push-preparations-0000001727885250#section388942317518
b. Configure the certificate fingerprint:/consumer/cn/doc/app/agc-help-signature-info-0000001628566748#section5181019153511 If the above ways can not be solved, please capture the logs for analysis by the following way, contact /consumer/cn/support/feedback/#/:
1. Implementation: hdc hilog >.
2. Reproduction scenarios
3. Stopping script execution
4. Obtaining log information in the directory
5. Description of the problem:
Is the push VoIP call message and audio/video interface all built-in? Does the developer just need to configure a UI and nothing else?
Solution:
1, the audio and video page application needs to be customized, the document sample code provides page effects for development reference only, does not represent the final effect.
2, VoIP call message is responsible for pulling up the process of the application, in the process to complete the call status report pop-up call banner notification, listening to the call status callback, called page loading and other operations. Ringtone, vibration, audio and video effects need to be adapted by the developer.
/consumer/cn/doc/harmonyos-guides-V5/push-voip-V5
6. Description of the problem:
Notification of extended message embodiment:
push-type: 2
// Request Body
{
"payload": {
"extraData": "Extra data carried by the notification extension scenario", .
"notification": { .
"category": "EXPRESS",  .
"title": "Notification Title",
"body": "notice content",
"clickAction": { .
"actionType": 0
}
}
}
}
Will the notification part of the message be displayed as a notification? If so, what is the difference from the RemoteNotificationContent that onReceiveMessage will return?
Is the extraData part of the message passed by onReceiveMessage?
Solution:
- Notification----- this part of the message will be displayed as a notification?
will be displayed in the return in RemoteNotificationContent
/consumer/cn/doc/harmonyos-guides-V5/push-send-extend-noti-V5
- Is the extraData------ part of the message passed by onReceiveMessage?
Extended messages are available via onReceiveMessage.
/consumer/cn/doc/harmonyos-references-V5/push-remote-extension-ability-V5?catalogVersion=V5
- What is the result if onReceiveMessage returns null?
It's possible that you don't have permission to extend the message
/consumer/cn/doc/harmonyos-guides-V5/push-apply-right-V5#section159981112245