All Products
Search
Document Center

Manage messages

Last Updated: Apr 29, 2021

The message list shows the relevant information of simple push and template push messages created in the last 30 days. You can query the historical messages of simple push, template push and multiple push, while the broadcast messages cannot be queried on the console.

View message list

Log in to the mPaaS console, select the App and perform the following steps to view the message list:

  1. On the left-side navigation pane, choose Message Push Service.
  2. Click the Message list tab on the right side of the page.

    1
    Messages are sorted in descending order by creation time. The information displayed in the list includes:

    • Customer message ID: Customized by user or automatically generated by system
    • Push type: The push type of a message.
      User dimension: The message is pushed based on user ID.
      Device ID_Android: The message is pushed based on device ID and the push platform is Android.
      Device ID_iOS: The message is pushed based on device ID and the push platform is iOS.
    • Target ID: User ID or device ID.
    • Message title: The title of a message.
    • Creation time: The time when the message was successfully created, accurate to seconds.

View push details

To view push details of a message, click the Expand button (Expand button) of the target message on the list.

Then the following information appears:

  • Message ID: The unique identifier of a message automatically generated by MPS.
  • Push status: Shows the push status of a message. To learn the status codes and corresponding description, see Message push status codes.
  • Expiry time: the time when a message expires. The system automatically calculates the value based on the creation time and validity period of the message. If a message has not been sent successfully and remains in the DeviceNotOnlineOrNoResponse or NoBindInfo status, MPS will resend it after the device is connected or a user binding request is initiated. However, if the message expires, MPS will not resend it.
  • Modification time: the time when the push status of a message changes, accurate to seconds.

Search messages

You can search the message list for a message based on Target ID (Device ID or User ID) and Customer message ID. The procedure is as follows:

  1. In the search box displayed in the upper right corner of the Message list page, enter a complete device ID/user ID and customer message ID.
  2. Click the search icon (1) or press Enter. Only the message with the specified target ID and customer message ID is returned.
Note:
  • You can only search for Simple push, Template push, and Multiple push messages created in the last 30 days.
  • Multiple push messages are not displayed by default, but you can search for them.
  • Broadcast push messages are not displayed and cannot be searched for.

Message push status codes

The following tables list the common status codes and the possible status codes for various push channels.

Common status codes

Status code Message Description
-1 WaitingForVerify Waiting for verification.
0 DeviceNotOnlineOrNoResponse Waiting for the device to go online (the persistent connection between the target device and the message push gateway is closed) or waiting for delivery confirmation.
1 NoBindInfo There is no binding relationship. When you push a message based on the user ID, make sure that the target user ID has been bound with a device ID.
2 Acked When you use an MPS self-built channel to push a message, this status indicates that the message has been successfully pushed to the client.
When you use a third-party channel to push a message, this status indicates that the third-party push gateway has been successfully called.
99999999 NONE Unknown status.

Apple Push

Status code Message Description
2001 PayloadEmpty The message payload is empty.
2002 PayloadTooLarge The message payload is too large.
2003 BadTopic Incorrect bundleid in the certificate.
2004 TopicDisallowed Ilegal bundleid in the certificate.
2005 BadMessageId Incorrect messageId.
2006 BadExpirationDate Invalid expiration date.
2007 BadPriority Invalid priority.
2008 MissingDeviceToken Device token missed.
2009 BadDeviceToken The device token is invalid or in incorrect format, or it does not exist. When you push a message based on the user dimension and receive this status code, you need to check whether the token used for binding is correct or not. We recommend that you create a simple push message in the MPS console as a test after completing the binding.
In the development environment (the console is configured with a development environment certificate), you need to use your personal development certificate to package the App for testing. Otherwise, BadDeviceToken will appear.
2010 DeviceTokenNotForTopic The device token doesn’t match the specified topic.
2011 Unregistered Invalid token.
2013 BadCertificateEnvironment The client certificate is for the wrong environment.
2014 BadCertificate The certificate is invalid.
2023 MissingTopic No topic is specified.
2024 ConnClosed APNS disconnected. This status may caused by the following reasons:
  • The iOS push environment configured in the console and the pushed device token do not match.
  • The certificate packaged in the App’s installation package and the certificate configured in the console do not match.
  • The BundleId in the project is different from the BundleId configured in the console.
For more information about how to configure the iOS push certificate, environment and BundleId in the console, see iOS push certificate configuration.
2025 ConnUnavailable APNS connection is unavailable.

For more message push statuses of Apple Push, see Handling Notification Responses from APNs.

Huawei Push

Status code Description
100 Invaid unkown parameter.
101 Invaid API_KEY.
102 Invaid SESSION_KEY.
106 The App or Session has no permission to call the current service.
107 Obtain the client and secret again (e.g., in case of an updated algorithm).
109 Excessive nsp_ts difference
110 Interface internal exception.
111 Server is busy.
80000003 Terminal is not online.
80000004 The App has been uninstalled.
80000005 Response timed out.
80000006 No routing. No connection has been established between the terminal and Push.
80000007 The terminal is in other region, and doesn’t use Push in Mainland China.
80000008 Incorrect routing. It may because that the terminal has swithed the Push server.
80100000 Some parameters are incorrect.
80100002 Ilegal token list.
80100003 Ilegal payload.
80100004 Invalid timeout period.
80300002 No permission to send messages to the tokens listed in the parameter.
80300007 All tokens in the request are illegal tokens.
81000001 Internal error.
80300008 Authentication error (the request message body is too large).

MiPush

Status code Description
1001 System error.
10002 Service suspended.
10003 Error in remote service.
10004 Cannot request this resource due to IP restriction.
10005 This resource requires authroized appkey.
10008 Incorrect parameters.
10009 The system is busy.
10012 Ilegal request.
10013 Ilegal user.
10014 Access to the App interface is restricted.
10017 Ilegal parameter value.
10018 The request exceeds the length limit.
10022 Requests to the IP exceed the frequency limit.
10023 User’s requests exceed the frequency limit.
10024 User’s requests for special interface exceed the frequency limit.
10026 The App is in the blacklist, and cannot call any APIs.
10027 The App API is called too frequently.
10029 Illegal device.
21301 Authentication failed.
22000 Illegal App.
22001 The App doesn’t exist.
22002 The App has been revocated.
22003 Failed to update the App.
22004 App information missed.
22005 Invalid App name.
22006 Invalid App ID.
22007 Invalid App Key.
22008 Invalid App Secret .
22020 Illegal App description.
22021 The App hasn’t been authorized by users.
22022 Invalid App package name.
22100 Incorrect data format for the App notification.
22101 Too many App notifications.
22102 Failed to send the App notification.
22103 Invalid App notification ID.
20301 Invalid target.

OPPO Push

Status code Message Description
-1 Service Currently Unavailable The service is unavailable, please try again later.
-2 Service in Flow Control The service is under traffic control.
11 Invalid Auth Token Invalid AuthToken.
13 App Call Limited App calling counts exceed limit, including the calling frequency limit.
14 Invalid App Key Invalid AppKey.
15 Missing App Key AppKey missed.
16 Invalid Signature Invalid signature. Failed to pass signature verification.
17 Missing Signature17 Signature missed. Failed to pass signature verification.
28 App Disabled The App is unavailable.
29 Missing Auth Token AuthToken missed.
30 Api Permission Denied The App has no permission to perform API push.
10000 Invalid RegistrationId registration_id is in incorrect format.

vivo Push

Status code Description
10000 Permission authentication failed.
10040 The resouce has reached the upper limit, please try again later.
10050 Both alias and regId cannot be empty.
10055 The title cannot be empty.
10056 The title cannot exceed 40 characters in length.
10058 The content cannot exceed 100 characters in length.
10066 The number of custom key/value pairs cannot exceed 10.
10067 Invalid custom key/value pair.
10070 The total number of messages sent exceeds the limit.
10071 The sending time is out of the allowable time range.
10072 Message push is too fast, please try again later.
10101 The message content is unapproved.
10102 Unkown exception occured in vivo server.
10103 Pushed content contains sensitive information.
10110 Please set the frequency of sending commercial messages.
10302 Invalid regId.
10303 requestId already exists.
10104 Please send a formal message. Please check the content, and do not send test text. The content in a formal message should not be numbers only, letters only, symbols plus numbers,and cannot contain “test”, braces, and square brackets.

FCM

Status code Message Description
90000002 InvalidRegistration Invalid target.
90000003 NotRegistered The target is unregistered.
90000004 InvalidPackageName Invalid package name.
90000007 MessageTooBig Message body is too large.
90000009 InvalidTtl Invalid offline time-to-live.
90000011 InternalServerError FCM service exception
90000401 Authentication Failed to pass permission verification.