1. Problem description:
Is the length of pushdeviceid fixed?
Solution:
In the Hongmeng system, the length of the device ID is fixed.
2. Problem description:
Through the REST API, IM-type messages are pushed by three parties, how to achieve the application not displaying the three-party push notification when it is in the foreground.
Solution:
If the developer's application process is in the foreground, no notification reminder will pop up. The developer can obtain the content of the notification extension message in the application process and complete the business processing by himself.
Send notification extension message:/consumer/cn/doc/harmonyos-guides-V5/push-send-extend-noti-V5
3. Problem description:
The push of Hongmeng manufacturers channel has relatively large delays, with significantly lower speeds than Android and Apple devices, and the delay time of different Hongmeng devices is significantly different.
Solution:
There is a significant difference in delay time between Hongmeng equipment.
Through server inspection, it was found that the pushed messages were marketing notifications. Not every marketing message was sent directly, but a batch would be sent together. It is a message mechanism for Huawei to push the server to reduce power consumption. Some of the early test models may not have this mechanism, but the subsequent models will have such control measures.
It will not affect the arrival of the message. It will just wait until the number of current online marketing notifications reaches a certain amount before pushing them together, which will cause a certain delay.
If the developer does not want to be delayed, it is recommended to refer to the document to apply for the corresponding self-categorized rights and push the message body to set the corresponding category key-value pair. In this way, the message is a service notification, and it is not controlled and delivered in a timely manner.
/consumer/cn/doc/harmonyos-guides-V5/push-apply-right-V5#section15173623155816
4. Problem description:
About HarmonyOS NEXT Picture Risk Control API interface function confirmation, interface document:/consumer/cn/doc/harmonyos-references/push-image-control-0000001775689565
1. According to the document, this interface currently supports projectid and clientid. Will these two methods be stable in the future?
2. Will the functional performance be different when using projectid and clientid?
Solution:
1. Currently, there are two methods of supply that are provided to choose from based on the business. There is currently no clear plan for the later support situation.
2. The functional performance is the same.
5. Problem description:
Install and log in to the app for the first time. Get notification permission and choose not to allow, and also obtain token registration promotion service. Then after opening notification permissions on the system settings page, you still cannot receive notifications. Since the token will be changed, the token registration process needs to be triggered again before receiving the notification. Can you solve this restriction and directly receive the notification?
Solution:
Whether a message is pushed to the device during the notification permission is closed, the device will be controlled after the notification permission is closed, and the message sent after the notification permission is controlled will not be delivered to the device. After the notification permission is opened again, it will be reported and released. In order to prevent users from frequently reporting and re-releasing the control, the current specification will be delayed by 1 minute. After the control is released, the message will be received without re-generating the token.
6. Problem description:
Push message receipt shows result: 256
Solution:
256 is the frequency limit of information marketing. The application has pushed multiple messages to this device within a certain period of time, and the marketing quota for the day has been consumed.