Push success
If the push is successful, you’ll see:
- Push success: A success message.
- Push channel: The vendor (RC or third-party) that sent the push request.
- Return status: Data returned by RongPush or the third-party vendor (for RC troubleshooting only, you can ignore this).
Push error codes
If the push fails, an error code will appear in the return status.
| Error code | Description |
|---|---|
| P16 | The message isn’t a built-in RC message type (see message type overview) and no push content (pushContent) is set, so it can’t be pushed. |
| P17 | The recipient has enabled global Do Not Disturb. |
| P19 | The recipient has enabled Do Not Disturb for a specific conversation. |
| P23 | The device ID is empty. |
| P60 | Encrypted message has no push content. |
| NotSupport | Not supported. |
| RONG_OFFLINE | Third-party token is empty, switched to Rong Push, but Rong Push is offline, so the push failed. |
| PUSH_A3 | Server-side issue: Device Token format is incorrect (length is less than 2). |
| PUSH_A4 | The client reported a third-party push token, but the token is empty. |
| PUSH_A5 | An error occurred during sending. The package might not be configured for third-party push. If the issue persists, contact RC developers. |
| PUSH_A7 | Server-side error: Failed to enqueue the push. |
| PUSH_A8 | Failed: Queue limit exceeded for OPPO, discarded. |
| PUSH_A11 | An error occurred during sending. Contact developers. |
| PUSH_A12 | Server-side push failed more than 3 times. |
| PUSH_A13 | Xiaomi Push server returned a non-200 HTTP response code. Push failed. |
| PUSH_A14 | An error occurred during sending. Contact developers. |
| PUSH_A16 | An error occurred during push sending. After 3 retries, it failed. |
| PUSH_A17 | An error occurred when switching to GCM. |
| PUSH_A18 | An error occurred when switching to FCM. |
| PUSH_A19 | Push failed: Unsupported push type. |
| PUSH_A23 | Package name, Push Token, or pushSecret is empty. Third-party push isn’t configured in the developer backend. |
| PUSH_A24 | pushParam is empty. |
| PUSH_A25 | Title or content is empty. |
| PUSH_A26 | Failed to send: secret is empty. Not configured in the developer backend. |
| PUSH_A27 | Failed to send: pushParam is empty. Huawei configuration is empty. |
| PUSH_A28 | Failed to send: hwId is empty. Huawei push configuration App ID is empty in the developer backend. |
| PUSH_A29 | Failed to send: Failed to get Huawei access token. Contact developers. |
| PUSH_A30 | Type is empty. |
| PUSH_A31 | Failed to parse the type parameter. |
| PUSH_A32 | V4 NotSupport touchuan Push. |
| PUSH_A33 | Huawei old push setting is disabled. |
| PUSH_A41 | mzSecret is empty. Not configured in the developer backend. |
| PUSH_A42 | pushParam is empty. |
| PUSH_A43 | MeiZu ID is empty. MeiZu push configuration App ID is empty in the developer backend. |
| PUSH_A44 | An error occurred during sending. Contact developers. |
| PUSH_A45 | Failed to send more than 3 times. Discarded. |
| PUSH_A46 | Rate limit exceeded. |
| PUSH_A47 | Failed to send. See response error. |
| PUSH_A49 | An error occurred during sending. Contact developers. |
| PUSH_A50 | Push sending rate limit exceeded. |
| PUSH_A61 | Failed to send: Master secret is empty. Not configured in the developer backend. |
| PUSH_A62 | pushParam is empty. |
| PUSH_A63 | Failed to send: OPPO AppKey is empty. |
| PUSH_A64 | Failed to send: Failed to get OPPO auth token. Check if the developer backend is configured with master secret or if the AppKey is incorrect. |
| PUSH_A65 | Failed to get auth token. Contact developers. |
| PUSH_A66 | An error occurred during sending. |
| PUSH_A71 | An error occurred during sending: Internal error. |
| PUSH_A81 | Failed to send: secret is empty. Not configured in the developer backend. |
| PUSH_A82 | pushParam is empty. |
| PUSH_A83 | Failed to send: appId is empty. Not configured in the developer backend. |
| PUSH_A84 | Failed to send: Failed to get VIVO auth token. |
| PUSH_A85 | An error occurred during sending. |
| PUSH_A87 | Failed to get auth token: Non-OK HTTP response. |
| PUSH_A88 | Failed to refresh auth token: Incorrect result value. |
| PUSH_A89 | Failed to refresh auth token: Non-OK HTTP response. |
| PUSH_A90 | Failed to refresh auth token: pushParam or secret is empty. |
| PUSH_A91 | Failed to get auth token: pushParam or secret is empty. |
| PUSH_A93 | Incorrect result. |
| PUSH_A95 | An error occurred during sending. Contact developers. |
| PUSH_I1 | Payload is empty. Discarded. Push content is empty. Contact developers. |
| PUSH_I2 | Push Token is empty. |
| PUSH_I3 | Payload is empty. Discarded. Push content is empty. Contact developers. |
| PUSH_I4 | Failed to enqueue the push due to maximum limit. Discarded. Contact developers. |
| PUSH_I5 | When switching to iOS push, the push content is empty. Contact developers. |
| PUSH_I6 | Failed to get HTTP connection. Check if the certificate is correct (usually a certificate issue). |
| PUSH_I7 | Connection is empty. Delayed re-enqueue. |
| PUSH_IEX | An error occurred during push sending. Contact developers. |
| PUSH_I9 | Certificate loading error: Discarded during the ban period. Check if the package has uploaded the iOS certificate. If yes, check the specific reason for the previous push failure. |
| PUSH_I10 | Failed to add to the sending queue. Contact developers. Check server error logs. |
| PUSH_I11 | Failed to load the certificate: Internal error. Contact developers. |
| PUSH_I12 | An error occurred during push sending. Contact developers. Server-side internal error. |
| PUSH_I15 | Unsupported terminal type. |
| Rong_DeviceToken_Invalid | iOS 13 system uses the old method to get the DeviceToken. |
| PUSH_I24 | Certificate loading: Failed to load AppInfo. |
| PUSH_I25 | Certificate loading: Failed to load AppInfoExt. |
| PUSH_I26 | Certificate loading: Failed to load AppDBInfo. |
| PUSH_I27 | Certificate loading: Failed to get certificate info. |
| PUSH_I28 | Certificate loading: An error occurred while loading certificate info. |
| PUSH_I29 | Failed to send: An error occurred. |
| PUSH_I30 | Push content is empty. |
| PUSH_I31 | Push feature is disabled. |
| PUSH_I32 | Global app push feature is disabled. |
| PUSH_I33 | Non-one-on-one app push feature is disabled. |
| PUSH_I34 | An error occurred while checking the push switch. |
| PUSH_I35 | Unknown error: Contact developers. |
| PUSH_I36 | Invalid iOS token. |
| PUSH_I37 | h2Client is null. |
| PUSH_I38 | h2Client hasn’t completed the handshake. |
| PUSH_I39 | Pool is null. |
| PUSH_IP8_1 | AppDBInfo for the appKey wasn’t found. |
| PUSH_IP8_2 | Failed to build HTTP client. Check if the p8 file, keyId, and teamId are correct. |
| PUSH_IP8_3 | Failed to add to the P8 sending queue. |
| PUSH_IP8_4 | An error occurred while adding to the P8 sending queue. |
| PUSH_IP8_5 | Failed to build p8 Notification push message body. |
| PUSH_IP8_ERR | Failed to send: BadDeviceToken. The build environment and AppKey don’t match. |
| APNS | APNS failure code. |
| APNS_A0 | Failed to send to APNS. Response failed. |
| APNS_A1 | Timed out while sending to APNS. |
| APNS_A2 | Other errors. |
| RONG_A2 | Device Token is empty when sending push to a third-party service. Switched to Rong Push, but the user is offline. Push failed. |
| RONG_A97 | Rong Push failed: Sending incomplete. Contact developers. |
| RONG_A98 | Rong Push failed. Contact developers. |
| RONG_A100 | An error occurred during Rong Push sending. Contact developers. |
| RONG_A101 | Rong Push failed. Contact developers. |
| I5 | Push content is empty. |
| I19 | Unsupported event tracking type. |
| PUSH_A86 | Failed to send: Failed to get auth token. Incorrect result value. |
| PUSH_NO_INTENT | Failed to send: The intent parameter isn’t set in the RC developer backend. |
| PUSH_INTENT_NO_END | The intent parameter is incorrectly set. It doesn’t end with “end”. |
| GCMNotSupport | GCM NotSupport. |
| RONG_A102 | Third-party push token wasn’t reported. Switched to Rong Push, but Rong Push is offline. Push failed. Check the Android logs to see why the third-party token wasn’t set. If the token is set, check if the token, package name, and AppKey match. |
| APNS_4_4_null | Check the logs above. If ex=expire and the time is earlier than the current time, the certificate has expired. If ex=null, check if the iOS certificate is configured. If the time hasn’t expired, get the full logs from the message node and check the push service with the session ID. |
| APNS_A2_2_400_{“reason”:“BadDeviceToken”} | Push failed with BadDeviceToken error. Reason: You’re using a production environment iOS certificate, but your app is built in the test environment. Solutions: 1. Re-upload the iOS test environment certificate. It’ll take effect in 30 minutes. 2. Build your app in the production environment. |
Xiaomi push error codes
| Error code | Description |
|---|---|
| MI_A1 | Xiaomi response code isn’t successful. |
| MI_A2 | Xiaomi response body is empty. Contact developers. |
| MI_A3 | Xiaomi response status code isn’t 200. Contact developers. |
The following are official Xiaomi push response codes.
MI is the prefix, ‘_’ is followed by the Xiaomi push platform response code. If it’s not found in this document, it might be newly added on the Xiaomi official website.
Xiaomi developer platform - Server error code reference
| Error code | Description |
|---|---|
| MI | Xiaomi response code. |
| MI_-1 | Unknown error. |
| MI_1 | Internal error. |
| MI_10001 | System error. |
| MI_10002 | System busy. |
| MI_10003 | Remote service error. |
| MI_10008 | Parameter error. Refer to the API documentation. |
| MI_10012 | Illegal request. |
| MI_10013 | Invalid user. |
| MI_10016 | Missing required parameter. |
| MI_10017 | Invalid parameter value. |
| MI_10027 | The app’s API calls are too frequent. |
| MI_10029 | Invalid device. |
| MI_10030 | The app is fetching invalid regid too frequently. |
| MI_10031 | The app is in the blacklist and can’t send messages. |
| MI_10032 | The app is fetching invalid alias too frequently. |
| MI_10033 | The app is in the blacklist and can’t send feedback requests. |
| MI_10034 | The app has sent too many messages today. |
| MI_10035 | No more invalid alias to fetch. |
| MI_10036 | The app’s operation is prohibited. |
| MI_10037 | Request expired. |
| MI_10038 | The app is prohibited from accessing statistics and trace data. |
| MI_10039 | The app is fetching message statistics and trace too frequently. |
| MI_10040 | Small Icon image link or color value is empty. |
| MI_20004 | Invalid user. |
| MI_20607 | DB error. |
| MI_20209 | Invalid topic. |
| MI_20215 | Failed to subscribe to the topic. |
| MI_20216 | Failed to unsubscribe from the topic. |
| MI_20301 | Failed to send the message. |
| MI_20315 | Failed to delete the broadcast message. |
| MI_21301 | Authentication failed. |
| MI_21302 | Token authentication failed. |
| MI_21303 | Restricted request. |
| MI_21305 | Missing required parameter. |
| MI_22000 | Invalid app. |
| MI_22006 | Invalid app ID. |
| MI_22007 | Invalid app Key. |
| MI_22022 | Invalid app package name. |
| MI_22102 | Failed to send app notification message. |
| MI_26003 | Internal push call failed. |
| MI_26004 | Broadcast message sent too frequently. |
| MI_26005 | Account setting is too frequent and is prohibited. |
| MI_26006 | The message needs to be reviewed. Please review it promptly. |
| MI_26007 | Failed to query smallIcon. |
| MI_65003 | Device not found. |
| MI_65006 | Alias setting is too frequent and is prohibited. |
| MI_65007 | Alias is in the blacklist. |
| MI_65008 | Alias is too long. |
| MI_65009 | Message content is too long. |
| MI_65010 | Topic is too long. |
| MI_65011 | Parameter not provided. |
| MI_65012 | Alias is empty. |
| MI_65013 | Topic is empty. |
| MI_65014 | Too many key-value pairs. |
| MI_65015 | Total key-value pair length is too long. |
| MI_65016 | User account is empty. |
| MI_65017 | User account is too long. |
| MI_65020 | APNS certificate password is incorrect. |
| MI_65021 | APNS certificate has expired. |
| MI_65022 | APNS certificate isn’t effective yet. |
| MI_65023 | APNS certificate is incorrect. |
| MI_65024 | Can’t find the corresponding algorithm to parse the APNS certificate. |
| MI_65025 | APNS certificate isn’t uploaded. |
| MI_65026 | APNS certificate unknown error. |
| MI_65027 | APNS certificate type mismatch. |
| MI_65028 | Can’t find the corresponding message. |
| MI_65029 | Remote service error. |
| MI_65030 | An error occurred while building JSON. |
| MI_65031 | The certificate isn’t issued by Apple. |
| MI_65032 | Certificate usage error. |
| MI_65033 | Doesn’t contain a valid certificate. |
| MI_65034 | Contains too many certificates. |
| MI_65035 | Too many topics. |
| MI_65036 | Callback parameter is too long. |
| MI_65037 | Callback URL is too long. |
| MI_65038 | Callback URL is invalid. |
| MI_65039 | Registration failed. Refers to iOS device registration error. |
| MI_65040 | Logout failed. |
| MI_65041 | ImeiMd5 is empty. |
| MI_65042 | ImeiMd5 is invalid. |
| MI_66006 | Registration failed. Refers to Android device registration error, including device and app registration. |
| MI_66007 | Invalid RegId. |
| MI_66008 | Invalid request. |
| MI_66108 | Invalid parameter information. |
| MI_66109 | Invalid regSecret. |
| MI_66300 | Unknown command. |
| MI_66301 | Command execution error. |
| MI_66302 | Device token is empty. |
| MI_66303 | Xiaomi ID is empty. |
| MI_66304 | Xiaomi ID is too long. |
| MI_66305 | Invalid Xiaomi ID. |
| MI_66306 | Failed to enable or disable push. |
| MI_66307 | Invalid message ID when deleting a scheduled job. |
| MI_66308 | Invalid scoring service request parameter. |
| MI_70011 | Input is empty. |
| MI_70012 | Invalid JobKey format. |
| MI_200001 | Push count exceeds the daily limit. |
| MI_200002 | Push QPS exceeds the limit. |
Huawei push error codes
Huawei push error codes
| Error code | Description |
|---|---|
| HW_A25 | Failed to parse Huawei response. Contact RC developers. |
| HW_A26 | Invalid access token. Contact developers. |
| HW_A27 | Check the returned error code. If the code is 80300007, the token reported by the client might use a different AppKey than the one used to send the message. |
The following are official Huawei push response codes.
HW is the prefix, ‘_’ is followed by the Huawei push platform response code. If it’s not found in this document, it might be newly added on the Huawei official website.
Huawei developer platform - Server error code reference
| Error code | Description |
|---|---|
| HW_500 | Server system error. |
| HW_503 | Flow control error: Sending rate is too high. |
| HW_6 | Session expired. |
| HW_102 | Invalid SESSION_KEY. |
| HW_105 | Parameter error. |
| HW_111 | System or service is busy. |
| HW_112 | Can’t find the corresponding service. |
| HW_113 | Failed to request the service. |
| HW_114 | Service is unreachable or no route. |
| HW_199 | Unknown error. |
| HW_403 | No permission. |
| HW_80100000 | Parameter check error. |
| HW_80100001 | Token parameter check error. |
| HW_80100002 | Invalid token list. |
| HW_80100003 | Invalid payload. |
| HW_80100004 | Invalid timeout. |
| HW_80100012 | Cache type setting error. |
| HW_80100013 | Cache resend parameter setting error. |
| HW_80100016 | The message contains sensitive information. |
| HW_80200001 | Oauth authentication error. |
| HW_80200003 | Oauth Token expired. |
| HW_80300002 | No permission to send messages to the token list in the parameter. |
| HW_80300004 | Authentication error. |
| HW_80300005 | Authentication error (The local configuration group doesn’t match the requested group). |
| HW_80300007 | Authentication error (All TOKENs in the request are invalid). |
| HW_80300008 | Authentication error (The request message body is too large). |
| HW_80300010 | Authentication error (Too many TOKENs). |
| HW_81000001 | Unknown error. |
OPPO push error codes
| Error code | Description |
|---|---|
| OPPO_A0 | OPPO response body is abnormal. Contact developers. |
| OPPO_A1 | OPPO ### OPPO push error codes |
| Error code | Description |
|---|---|
| OPPO_A0 | OPPO ResponseBody anomaly - contact developer |
| OPPO_A1 | OPPO app authentication failed |
| OPPO_A2 | OPPO unsuccessful response code |
| OPPO_A3 | OPPO HTTP response code unsuccessful |
Official OPPO push response codes
OPPO prefix, followed by ‘_’ and the OPPO push platform response code. If not listed here, it may have been recently added to the OPPO official website.
OPPO developer platform - server error code reference
| Error code | Description |
|---|---|
| OPPO_-2 | Server traffic control |
| OPPO_-1 | Service unavailable - try again later |
| OPPO_11 | Invalid AuthToken |
| OPPO_12 | Incorrect HTTP method |
| OPPO_13 | App call limit exceeded, including frequency limit |
| OPPO_14 | Invalid AppKey parameter |
| OPPO_15 | Missing AppKey parameter |
| OPPO_16 | Sign verification failed - invalid signature |
| OPPO_17 | Missing signature parameter |
| OPPO_18 | Missing timestamp parameter |
| OPPO_19 | Invalid timestamp parameter |
| OPPO_20 | Non-existent method name |
| OPPO_21 | Missing method name parameter |
| OPPO_22 | Missing version parameter |
| OPPO_23 | Invalid version parameter - must be numeric |
| OPPO_24 | Unsupported version number |
| OPPO_25 | Encoding error - usually caused by non-UTF-8 HTTP requests |
| OPPO_26 | IP blacklist |
| OPPO_27 | No permission for this function - access denied |
| OPPO_28 | App unavailable |
| OPPO_29 | Missing AuthToken parameter |
| OPPO_30 | App lacks API push permission |
| OPPO_31 | Data doesn’t exist |
| OPPO_32 | Data duplication |
| OPPO_33 | Message count exceeds daily limit |
| OPPO_34 | Image upload exceeds daily limit |
| OPPO_40 | Missing required parameter - refer to API docs |
| OPPO_41 | Parameter error - check format and range |
| OPPO_51 | Invalid image - check format and upload method |
VIVO push error codes
| Error code | Description |
|---|---|
| VIVO_A0 | Unsuccessful business code response. If error code 10302, this device isn’t a test user - add test device on VIVO developer platform |
| VIVO_A1 | HTTP unsuccessful response code |
Official VIVO push response codes
VIVO prefix, followed by ‘_’ and the VIVO push platform response code. If not listed here, it may have been recently added to the VIVO official website.
VIVO developer platform - server error code reference
| Error code | Description |
|---|---|
| VIVO_10000 | Permission authentication failed |
| VIVO_10006 | Alias exceeds 40 characters |
| VIVO_10007 | AppKey doesn’t exist during alias subscription |
| VIVO_10040 | Resource limit reached - try again later |
| VIVO_10050 | Alias and regId can’t both be empty |
| VIVO_10051 | Unsupported message type |
| VIVO_10054 | Invalid notifyType |
| VIVO_10055 | Title can’t be empty |
| VIVO_10056 | Title exceeds 40 characters |
| VIVO_10057 | Content can’t be empty |
| VIVO_10058 | Content exceeds 100 characters |
| VIVO_10059 | Invalid timeToLive |
| VIVO_10060 | Invalid skipType |
| VIVO_10061 | skipType = 2 - skipContent can’t be empty |
| VIVO_10062 | skipType = 2 - skipContent exceeds 1000 characters |
| VIVO_10063 | skipType = 3 - skipContent can’t be empty |
| VIVO_10064 | skipType = 3 - skipContent exceeds 1024 characters |
| VIVO_10065 | Invalid networkType |
| VIVO_10066 | Custom key-value pairs exceed 10 |
| VIVO_10067 | Invalid custom key-value pairs |
| VIVO_10068 | skipType = 4 - skipContent can’t be empty |
| VIVO_10069 | skipType = 4 - skipContent exceeds 1024 characters |
| VIVO_10070 | Total send volume exceeds limit |
| VIVO_10071 | Exceeds allowed send time range |
| VIVO_10072 | Push speed too fast - try again later |
| VIVO_10101 | Message content review failed |
| VIVO_10103 | Push content contains sensitive info |
| VIVO_10104 | Send official info - avoid test content |
| VIVO_10150 | Aliases and regIds can’t both be empty |
| VIVO_10151 | taskId can’t be empty |
| VIVO_10152 | Invalid taskId |
| VIVO_10153 | regIds count not in [2-1000] range |
| VIVO_10154 | Aliases count not in [2-1000] range |
| VIVO_10155 | Message doesn’t exist or has expired |
| VIVO_10200 | appId can’t be empty |
| VIVO_10201 | appKey can’t be empty |
| VIVO_10202 | Invalid appKey |
| VIVO_10203 | Timestamp can’t be empty |
| VIVO_10204 | Sign can’t be empty |
| VIVO_10205 | appId doesn’t exist |
| VIVO_10206 | Incorrect sign |
| VIVO_10207 | Invalid timestamp |
| VIVO_10250 | Authentication interface call limit exceeded |
| VIVO_10252 | Batch send message body exceeds limit |
| VIVO_10254 | Full send exceeds count limit |
| VIVO_10301 | Alias exceeds 40 characters |
| VIVO_10302 | Invalid regId - may have expired |
| VIVO_10303 | requestId already exists |
| VIVO_10304 | Extra contains unsupported key |
| VIVO_10305 | Extra callback exceeds 128 characters |
| VIVO_10306 | Extra callback.param exceeds 64 characters |
| VIVO_10307 | Invalid alias - may have expired |
| VIVO_10352 | requestId can’t be empty |
| VIVO_10353 | requestId exceeds 64 characters |
| VIVO_10471 | taskIds count exceeds 100 |
| VIVO_10472 | taskIds format error |
| VIVO_10473 | taskIds is empty |
| VIVO_10600 | Invalid name parameter - use Chinese, English, numbers, underscores; can’t start with number; max 50 characters |
| VIVO_10601 | Tag name can’t be empty |
| VIVO_10602 | Tag description exceeds 300 characters |
| VIVO_10603 | oldName parameter can’t be empty |
| VIVO_10604 | newName parameter can’t be empty |
| VIVO_10605 | Invalid oldName parameter - use Chinese, English, numbers, underscores; can’t start with number; max 50 characters |
| VIVO_10606 | Invalid newName parameter - use Chinese, English, numbers, underscores; can’t start with number; max 50 characters |
| VIVO_10607 | id parameter can’t be empty |
| VIVO_10608 | type parameter can’t be empty |
| VIVO_10609 | ids parameter can’t be empty |
| VIVO_10610 | Tag name already exists |
| VIVO_10611 | Tag category name already exists |
| VIVO_10612 | Tag combination name already exists |
| VIVO_10613 | Invalid group parameter - use Chinese, English, numbers, underscores; can’t start with number; max 50 characters |
| VIVO_10614 | ids count exceeds 1000 |
| VIVO_10615 | Tag count exceeds 100 |
| VIVO_10616 | Invalid type parameter |
| VIVO_10700 | userids can’t be empty |
| VIVO_10701 | userid count exceeds limit |
| VIVO_10702 | Invalid optionType |
| VIVO_10703 | Register interface call frequency exceeded - try again later |
| VIVO_10704 | Register call too fast - try again later |
| VIVO_10705 | App not supported |
| VIVO_10706 | Invalid userType |
| VIVO_10800 | registration_tokens count not in specified range |
| VIVO_10801 | Notification can’t be empty |
| VIVO_10802 | original_source_name can’t be empty |
| VIVO_10803 | Invalid original_source_name length |
| VIVO_10804 | original_source_ip can’t be empty |
| VIVO_10806 | Invalid click_action |
| VIVO_10807 | URL length exceeds limit |
| VIVO_10808 | Intent length exceeds limit |
Meizu platform
Meizu open platform PUSH system response
| Error code | Description |
|---|---|
| MEIZU_A48 | Send failed - see response error |
| MEIZU_500 | Other exceptions |
| MEIZU_1001 | System error |
| MEIZU_1003 | Server busy |
| MEIZU_1005 | Parameter error - refer to API docs |
| MEIZU_1006 | Signature authentication failed |
| MEIZU_110000 | Invalid appId |
| MEIZU_110001 | Invalid appKey |
| MEIZU_110004 | Parameter can’t be empty |
| MEIZU_110009 | App added to blacklist |
| MEIZU_110010 | App push rate too fast |
| MEIZU_110053 | Transmission exceeds limit |
New version push platform error codes
- Push failure error codes
- 1xxx indicates general error codes
- 2xxx indicates Xiaomi push error codes
- 3xxx indicates Huawei push error codes
- 4xxx indicates VIVO push error codes
- 5xxx indicates OPPO push error codes
- 6xxx indicates Meizu push error codes
- 7xxx indicates FCM push error codes
- 8xxx indicates APNS push error codes
- 9xxx indicates Rong push channel
- 10xxx indicates Honor push channel (some older Honor devices and apps still use Huawei push channel)
| Error code | Description |
|---|---|
| 1xxx | General error codes |
| 1000 | Internal service exception |
| 1001 | Invalid token string length |
| 1002 | pushType or token is empty |
| 1003 | Send failure count exceeds maximum threshold |
| 2xxx | Xiaomi push error codes |
| 2000 | packageName or token or pushSecret is empty |
| 2001 | Developer console push related parameters are empty |
| 2002 | Third-party push interface returned HTTP Status Code non-200 |
| 2003 | Third-party push interface returned failure |
| 2004 | Third-party push interface returned empty ResponseBody |
| 2005 | Third-party push interface ResponseBody parsing exception |
| 2006 | Push title or content is empty |
| 2007 | Batch push interface returned partial failure |
| 3xxx | Huawei push error codes |
| 3000 | token or hwSecret is empty |
| 3001 | Developer console push related parameters are empty |
| 3002 | hwId is empty |
| 3003 | intent is empty |
| 3004 | Invalid intent format |
| 3005 | Access token retrieval failed |
| 3006 | V4 interface no longer supports transmission push |
| 3007 | V1 push interface is deprecated |
| 3008 | Third-party push interface returned HTTP Status Code non-200 |
| 3009 | Third-party push interface returned failure |
| 3010 | Invalid or expired sessionKey |
| 3011 | Third-party push interface ResponseBody parsing exception |
| 3012 | Batch push interface returned partial failure |
| 4xxx | VIVO push error codes |
| 4000 | token or vivoAppSecret is empty |
| 4001 | Developer console push related parameters are empty |
| 4002 | vivoAppId is empty |
| 4003 | Access token retrieval failed |
| 4004 | Third-party push interface returned HTTP Status Code non-200 |
| 4005 | Third-party push interface returned failure |
| 4006 | Batch push interface returned partial failure |
| 5xxx | OPPO push error codes |
| 5000 | token or masterSecret is empty |
| 5001 | Developer console push related parameters are empty |
| 5002 | oppoAppkey is empty |
| 5003 | Access token retrieval failed |
| 5004 | Access token retrieval exception |
| 5005 | Third-party push interface returned HTTP Status Code non-200 |
| 5006 | Third-party push interface returned failure |
| 5007 | Batch push interface returned failure |
| 5008 | Batch push interface returned partial failure |
| 6xxx | Meizu push error codes |
| 6000 | token or mzSecret is empty |
| 6001 | Developer console push related parameters are empty |
| 6002 | mzId is empty |
| 6003 | Third-party push interface returned failure |
| 6004 | Batch push interface returned partial failure |
| 7xxx | FCM push error codes |
| 7000 | Third-party push interface returned failure |
| 7001 | projectId is empty |
| 7002 | Access token retrieval failed or is empty |
| 8xxx | APNS push error codes |
| 9xxx | Rong push channel |
| 9000 | User RONG PUSH long connection offline |
| 9001 | Send push exception |
| 9002 | Send push failed, send not completed |
| 9003 | Send push failed |
| 10xxx | Honor push channel |
| 10000 | token or secret is empty |
| 10001 | Developer console push related parameters are empty |
| 10002 | clientId is empty |
| 10003 | intent is empty |
| 10004 | Invalid intent format |
| 10005 | Access token retrieval failed |
| 10006 | appId is empty |
| 10008 | Third-party push interface returned HTTP Status Code non-200 |
| 10009 | Third-party push interface returned failure |
| 10010 | Invalid access token |
| 10011 | Third-party push interface ResponseBody parsing exception |
| 10012 | Batch push interface returned partial failure |