This function deconstructs typical push scenarios by type and assigns an independent value of push-type to each type. It provides scenario-specific capabilities for message delivery, governance, and differentiation, effectively improving message reach and user experience.
| push-type | Name | Description | Remarks |
|---|---|---|---|
| 0 | Alert message | Notification message. Badge update message: Only the badge is updated, and no notification is displayed. | You need to apply for the message self-classification permission. |
| 1 | Widget update | Widget update. | - |
| 2 | Text-to-speech message | After Push Kit starts the notification extension child process, you can process the text-to-speech service in the child process. | You need to apply for the text-to-speech message permission. |
| 6 | Background message | The device will transfer the message to the app if the app is currently running in the foreground. Otherwise, the message will be cached for later delivery after the app is launched. | - |
| 7 | Live view message | A live view is created, updated, or ended. | You need to enable Live View Kit |
| 10 | In-app call message | In-app call message. | You need to apply for the in-app call message permission. |
The message body cannot exceed 4096 bytes (excluding the push token). Otherwise, error code 80300008 will be returned.
Each project can push a maximum of 1,000 test messages per day network-wide. Formal messages have different quotas depending on the specific scenarios. For details, please refer to Message Frequency Control.