This topic describes the error codes for Mobile Push.
If an error occurs when you call a CloudPushService API, the onFailed() callback of CommonCallback returns the errorCode and errorMessage.
Error codes (V3.7.6 and later)
Push API layer error codes
Error code | Problem description | Note |
|---|---|---|
PUSH_00000 | success | - |
PUSH_10101 | Missing parameters | Check if the request parameters are correct. |
PUSH_10102 | Invalid parameters | Check if the request parameters are correct. |
PUSH_10103 | The server-side signature does not match the client-side signature. | Check if the push configuration is correct. |
PUSH_10104 | Tag-related error | Troubleshoot the issue based on the specific error message. If the issue persists, contact Alibaba Cloud technical support. |
PUSH_10105 | Alias-related error | Troubleshoot the issue based on the specific error message. If the issue persists, contact Alibaba Cloud technical support. |
PUSH_10106 | Internal server error | Contact Alibaba Cloud technical support with the specific error message. |
PUSH_10107 | Network I/O error |
|
PUSH_10108 | Response parsing error | Save the specific error message and contact Alibaba Cloud technical support for troubleshooting. |
PUSH_10109 | Network connection failed. Check your network configuration. | Check if the network is available. |
PUSH_10114 | Internal error | Save the specific error message and contact Alibaba Cloud technical support for troubleshooting. |
PUSH_10115 | Abnormal channel registration status | Save the specific error message and contact Alibaba Cloud technical support for troubleshooting. |
PUSH_10118 | Other API errors | Contact Alibaba Cloud technical support with the specific error message. |
PUSH_10119 | Initialization is not required for non-main processes. | This error is triggered when initialization is performed in a non-main process. You can ignore it. |
PUSH_10120 | Push registration timed out. | Save the specific error message and contact Alibaba Cloud technical support for troubleshooting. |
PUSH_10121 | Network request failed. Check if the network is available. |
|
PUSH_20101 | Invalid parameter input | Check if the input parameters of the request are correct. |
PUSH_20102 | Incorrect process name for the silence connection. The process name cannot be empty and must match the configuration in the manifest file. The system automatically sets the process name to the one configured in the manifest. | Enabling debug mode checks for this error. The process name cannot be modified. Do not change the component process configuration. |
PUSH_20103 | Invalid appversion parameter. Check your version number. The version number cannot be null and its length cannot exceed 32 characters. | Enabling debug mode checks for this error. Check if the application version number is too long. |
PUSH_20105 | The auxiliary process is not set for ChannelService. | Enabling debug mode checks for this error. Unless in a special scenario, check if you have modified the process configuration of the push component. |
PUSH_20106 | Core components are not configured. | Enabling debug mode checks for this error. Check if you have deleted the declaration of the push component. |
PUSH_20107 | The push service is shut down due to continuous crashes. |
|
PUSH_20108 | Not initialized. Call the init method of PushServiceFactory first. | Confirm that the initialization was successful. |
PUSH_20109 | Deprecated API | See the CHANP document and use the appropriate API. |
PUSH_20110 | Registration has been called. Repeated calls are invalid. |
|
PUSH_ACCS_123 | ACCS error message | The format is ACCS_123, where 123 is the ACCS error code. Troubleshoot the issue based on the ACCS error code. |
PUSH_xxx | AGOO error message | The format is AGOO_xxx, where xxx is the AGOO error code. Troubleshoot the issue based on the AGOO error code. |
Push protocol layer (AGOO) error codes
Error code | Problem description | Note |
|---|---|---|
EAGOO_SDK_success | success | - |
EAGOO_SDK_remove_alias_fail_no_token | Failed to remove the alias. No alias record is found locally. |
|
EAGOO_SDK_remove_alias_fail_no_alias | Failed to remove the alias. No alias record is found locally. | 1. Check if the entered alias is correct. 2. This error may occur in earlier versions of Mobile Push. If you add an alias and then clear the application data, the alias information stored in the SDK is lost and cannot be removed. |
EAGOO_SDK_invalid_arg | Invalid request parameters | Check the input parameters. |
EAGOO_SDK_accs_disabled | ACCS check failed. |
|
EAGOO_SDK_agoo_not_bind | Register and initialize AGOO first. | Check if the initialization was successful. |
EAGOO_ACCS_123 | ACCS error message |
|
EAGOO_SERVER_XXX | Service error message |
|
Underlying push channel (ACCS) error codes
Error code | Problem description | Note |
|---|---|---|
200 | Success | - |
300 | Channel not established | Initialize bindApp before calling other APIs. |
-1 | Silence connection interrupted. Messages cannot be sent. | The system retries the connection internally. If the error persists, check whether the silence channel is working correctly. |
-2 | Parameter error. The message parameter is null. | Check whether the request parameters are correct. |
-3 | The service returned abnormal data. | Check the error message for the data returned by the service and contact Alibaba Cloud technical support to identify the cause. |
-4 | The data in a single request is too large. | Reduce the amount of data in a single request. The total data volume after encapsulation must be less than 16 KB. |
-5 | The service endpoint for sending messages is null. | Check whether the initialization configuration is correct. |
-6 | The authentication parameters for the silence channel persistent connection are incorrect. | Check whether the initialization parameter settings are correct. |
-7 | An authentication error occurred for the silence channel persistent connection. | Check the error message to identify the specific exception. |
-8 | An error occurred while sending data. | Check the error message to identify the specific exception. |
-9 | Message sending timed out. | Check the details to determine the cause of the timeout. |
-10 | The silence channel persistent connection is disconnected. | Check the previous logs to troubleshoot the disconnection. |
-11 | In-app persistent connection is disconnected. | This error is usually caused by a failure to establish a persistent connection. You must analyze the logs. |
-12 | Ping timed out for the silence channel persistent connection. | - |
-13 | No network connection. | Check the network connection. |
-14 | The appKey does not exist. | Check whether the initialization configuration is correct. |
-15 | The appSecret does not exist. | Check whether the initialization configuration is correct. |
70008 | The persistent connection sending queue is full. | Check whether messages are sent with high concurrency. If they are, limit the sending frequency. |
70020 | Low-level throttling | Confirm the throttling policy with the deployment engineer. |
70021 | High-level throttling. Messages are not sent. | Confirm the throttling policy with the deployment engineer. |
70023 | Throttling is triggered after an anti-spam unblock. Messages are not sent. | Confirm the throttling policy with the deployment engineer. |
102 | Invalid device | If this error occurs during testing, clear the application data and try again. |
302 | Invalid device | If this error occurs during testing, clear the application data and try again. |
303 | The AppKey configuration is incorrect. | Check whether the AppKey configuration is correct. |
304 | The package name is incorrect. | Check whether the appKey matches the application package name. |
-20 | The service returned an error. | Check the error message for the error code returned by the service and contact Alibaba Cloud technical support to identify the cause. |
-22 | The underlying SDK connection is closed. | Check the error message returned by the underlying SDK and contact Alibaba Cloud technical support to identify the cause. |
-23 | An error was returned when sending data. | Check the error message returned by the underlying SDK and contact Alibaba Cloud technical support to identify the cause. |
-25 | An unexpected fault | Check the error message for initialization errors. |
-26 | The connection establishment parameters are incorrect. | Check whether the initialization configuration is correct. |
-27 | Connection establishment timed out. |
|
-28 | Failed to establish a connection. |
|
-29 | The endpoint does not exist. | 1. The persistent connection address cannot be parsed on the current network. 2. Check whether the network is working correctly. |
-30 | An error occurred while establishing the connection. | Check the specific error message for troubleshooting. |
-10000 | Information about the underlying network library | If the error code is less than -10000, add 10000 to it to obtain the corresponding error code of the underlying network library. Troubleshoot the issue based on the underlying network library error code. |
Common error codes (V2.3.5 and later)
Error name | Error code | Description and solution |
|---|---|---|
MISSING_PARAM | 10101 | Missing parameters. Add the parameters based on the detailed error message. |
INVALID_PARAM | 10102 | Invalid parameters. View the detailed error message. |
SIGN_NOT_MATCH | 10103 | The server-side signature does not match the client-side signature. Check the AppKey and AppSecret. |
TAG_ERROR | 10104 | Tag request-related error. View the detailed error message. |
ALIAS_ERROR | 10105 | Alias-related error. View the detailed error message. |
INTERNAL_ERROR | 10106 | Internal server error. |
IO_ERROR | 10107 | Network I/O error. |
RESPONSE_PARSE_ERROR | 10108 | Response parsing error. |
CONNECTION_FAIL | 10109 | Network connection failed. Check your network configuration. |
SYSTEM_ERROR | 10110 | System error. |
UNKNOWN_ERROR | 10111 | Unknown error. |
NO_NETWORK | 10201 | Network unavailable. |
APPKEY_NULL | 10202 | Invalid AppKey. |
APPSECRET_NULL | 10203 | Invalid AppSecret. |
APPRECEIVER_NULL | 10204 | The callback function is empty. |
REG_TIME_OUT | 10205 | Request timed out. View the error-level logs with the `awcn` tag. |
CONN_INVALID | 10206 | The current connection is abnormal. |
NO_CONNECTION | 10207 | No network connection. View the error-level logs with the `awcn` tag. Check if the corresponding .so package is added. For more information, see What do I do if a "1105, unstable network or abnormal connection" error occurs? |
TAIR_ERROR | 10209 | Server error. |
INVALID_DEVICEID | 10210 | Invalid device ID. |
INVALID_PACKAGE | 10211 | The package name does not match the configuration. |
ACCS_CHANNEL_INIT_FAIL | 10212 | The silence connection process (the channel process by default) is not initialized. For more information, see Subsection 2 under "An exception suddenly occurs after a successful integration" in Android push failure troubleshooting steps. |
API_INVALID_INPUT | 20101 | Invalid parameters. See the specific error message for details. |
APP_VERSION_INVALID | 20103 | Invalid appversion parameter. Check your version number. The version number cannot be null and its length cannot exceed 32 characters. |
CHANNEL_PROCESS_NULL | 20105 | The auxiliary process is not set for ChannelService. |
REQUIRED_COMPONENT_NOT_EXISTS | 20106 | Core components are not configured. See the specific error message for details. |
CONTINOUS_CRASH | 20107 | The push service is shut down due to continuous crashes. |
Common error codes (V2.3.4 and earlier)
Error name | Error code |
|---|---|
NO_NETWORK | 1101 |
REG_FAIL | 1056 |
INVALID_APPKEY | 1052 |
INVALID_PACKAGENAME | 1053 |
INVALID_APPSECRET | 1054 |
NETWORK_UNSTABLE | 1105 |
INVALID_SERVER_RETURN | 1115 |
SYSTEM_UNKNOWN_ERROR | 1108 |