Error handling (3.x)

Updated at:

This document lists the error codes for Mobile Push Android SDK 3.x and includes legacy 2.x error codes for maintaining older apps. This information does not apply to 4.x.

Important

The error codes, ACCS/SPDY troubleshooting suggestions, and log filtering methods such as awcn described in this document apply only to versions earlier than 4.0.0. Version 4.x uses the ACCS proprietary channel and the unified EMAS_PUSH log tag. To troubleshoot API callback errors and connection issues for version 4.x, see Error handling (4.x).

If a call to the CloudPushService interface fails, you can get the errorCode and errorMessage from the CommonCallback's onFailed() callback.

Error codes (V3.7.6 - V4.0.0)

  • push interface error codes

Error code

Description

Remarks

PUSH_00000

success

-

PUSH_10101

Missing parameter

Check if the request parameters are correct.

PUSH_10102

Invalid parameter

Check if the request parameters are correct.

PUSH_10103

Server signature does not match the client signature

Check if the push configuration is correct.

PUSH_10104

Tag-related error

Troubleshoot based on the specific error message. If the issue persists, contact Alibaba Cloud Technical Support.

PUSH_10105

Alias-related error

Troubleshoot based on the specific error message. If the issue persists, contact Alibaba Cloud Technical Support.

PUSH_10106

Internal server error

Provide the specific error message when contacting Alibaba Cloud Technical Support.

PUSH_10107

Network I/O error

  1. Check if the network is available.

  2. Troubleshoot based on the specific error message. If the issue persists, contact Alibaba Cloud Technical Support.

PUSH_10108

Response parsing error

Save the specific error message and contact Alibaba Cloud Technical Support.

PUSH_10109

Network connection failed.

Check your network configuration and ensure the network is available.

PUSH_10114

Internal error

Save the specific error message and contact Alibaba Cloud Technical Support.

PUSH_10115

Unexpected channel registration status

Save the specific error message and contact Alibaba Cloud Technical Support.

PUSH_10118

Other API error

Provide the specific error message when contacting Alibaba Cloud Technical Support.

PUSH_10119

Initialization is not required for non-main processes

This error occurs when you initialize the service in a non-main process. You can ignore this error.

PUSH_10120

Push registration timed out

Save the specific error message and contact Alibaba Cloud Technical Support.

PUSH_10121

Network request failed.

  1. Check if the network is available.

  2. Troubleshoot based on the specific error message. If the issue persists, contact Alibaba Cloud Technical Support.

PUSH_20101

Invalid parameter

Check if the request parameters are correct.

PUSH_20102

Invalid process name for silent connection.

The process name cannot be empty and must match the one in the manifest file. The SDK validates this in debug mode. This version does not support changing the process name, so you must keep the default component process configuration.

PUSH_20103

Invalid appversion parameter.

This check is performed in debug mode. The application version number cannot be null and must not exceed 32 characters in length.

PUSH_20105

No helper process is configured for ChannelService

This check occurs in debug mode. Unless required by a specific use case, verify that the process configuration of the push component has not been modified.

PUSH_20106

Core component is not configured

This check occurs in debug mode. Verify that you have not deleted the declaration of the push component.

PUSH_20107

Push service disabled due to consecutive crashes

  1. The push service is disabled on startup if the application previously crashed after push initialization. Check the application's crash logs.

  2. In development or testing, if you trigger this error manually, clear the application data to restore the service.

  3. In a production environment, the service attempts to recover automatically. If the application continues to crash, you must upgrade the application version to restore the service.

PUSH_20108

Not initialized.

Call the init method of PushServiceFactory to initialize the SDK.

PUSH_20109

Deprecated API

Refer to the CHANP documentation and use the appropriate API.

PUSH_20110

Duplicate registration call.

  1. The SDK automatically retries failed registration attempts. You usually do not need to call the method again.

  2. If your application needs to re-register, wait for the register call to return two consecutive failed callbacks to confirm that the internal SDK retries have also failed. Then, call PushControlService.reset before calling register again.

PUSH_ACCS_xxx

ACCS error message

The format is PUSH_ACCS_xxx, where xxx is the ACCS error code. Troubleshoot the issue based on the specific ACCS error code.

PUSH_AGOO_xxx

AGOO error message

The format is PUSH_AGOO_xxx, where xxx is the AGOO error code. Troubleshoot the issue based on the specific AGOO error code.

  • AGOO layer error codes

Error code

Description

Notes

EAGOO_SDK_success

success

-

EAGOO_SDK_remove_alias_fail_no_token

Failed to remove the alias. No local alias record exists.

  1. Verify that the input alias is correct.

  2. This error can occur in earlier SDK versions. If you clear the application's data after adding an alias, the locally stored alias information is lost, preventing its removal.

EAGOO_SDK_remove_alias_fail_no_alias

Failed to remove the alias. No local alias record exists.

Verify that the input alias is correct. In some earlier SDK versions, if the application data is cleared after an alias is added, the locally stored alias information is lost, causing the removal to fail.

EAGOO_SDK_invalid_arg

Invalid request parameter.

Check the input parameters.

EAGOO_SDK_accs_disabled

ACCS check failed.

  1. Verify that the initialization was successful.

  2. Verify that the configuration is correct.

  3. Ensure the request is made in the main process.

EAGOO_SDK_agoo_not_bind

Register and initialize Agoo first.

Verify that the initialization was successful.

EAGOO_ACCS_123

ACCS error message.

  1. This indicates an error from the underlying push channel.

  2. The format is EAGOO_ACCS_123, where 123 represents the channel-specific error code. Use this code to troubleshoot the issue.

EAGOO_SERVER_XXX

Service error message.

  1. The push service returned an error. Contact technical support to troubleshoot the issue.

  2. The format is EAGOO_SERVER_XXX, where XXX represents the specific push service error code. Contact Alibaba Cloud Technical Support for assistance.

  • ACCS error codes

Error code

Description

Remarks

200

Success

-

300

Channel not established.

Initialize with bindApp before calling other APIs.

-1

Silent channel disconnected; messages cannot be sent.

The SDK retries automatically. If the error persists, verify that the silent channel is functioning correctly.

-2

Invalid parameter. The msg parameter is null.

Ensure the request parameters are correct.

-3

Unexpected data returned by the service.

Record the service data from the error message and contact Alibaba Cloud Technical Support to troubleshoot the issue.

-4

The data payload is too large.

Reduce the amount of data sent in a single request. The total payload size after packaging must be less than 16 KB.

-5

The service address is null.

Ensure the initialization configuration is correct.

-6

Invalid authentication parameters for the silent channel persistent connection.

Ensure the initialization configuration is correct.

-7

Authentication exception for the silent channel persistent connection.

Review the error message for details.

-8

An exception occurred while sending data.

Review the error message for details.

-9

Message sending timed out.

Review the logs to determine the cause of the timeout.

-10

Silent channel persistent connection disconnected.

Review the logs to determine the cause of the disconnection.

-11

In-app persistent connection disconnected.

This is usually caused by a failed attempt to establish the persistent connection. Review the logs for more details.

-12

Silent channel persistent connection ping timed out.

-

-13

No network connection.

Verify network connectivity.

-14

The appKey does not exist.

Ensure the initialization configuration is correct.

-15

The appSecret does not exist.

Ensure the initialization configuration is correct.

70008

Persistent connection send queue is full.

This error can occur with high message sending concurrency. Reduce the sending rate.

70020

Low-level rate limiting.

Record the error code and time of occurrence. Contact Alibaba Cloud Technical Support to review the rate limiting policy.

70021

High-level rate limiting. Message not sent.

Record the error code and time of occurrence. Contact Alibaba Cloud Technical Support to review the rate limiting policy.

70023

Rate limiting triggered after anti-abuse unblocking. Message not sent.

Record the error code and time of occurrence. Contact Alibaba Cloud Technical Support to review the rate limiting policy.

102

Invalid device.

If this occurs during testing, clear the application data and try again.

302

Invalid device.

If this occurs during testing, clear the application data and try again.

303

Invalid appKey configuration.

Ensure the appKey configuration is correct.

304

Invalid package name.

Ensure the appKey and the application package name match.

-20

Service returned an error.

Record the error code returned by the service, and contact Alibaba Cloud Technical Support to troubleshoot the issue.

-22

Underlying SDK connection closed.

Record the error message returned by the underlying SDK, and contact Alibaba Cloud Technical Support to troubleshoot the issue.

-23

An error occurred when sending data.

Record the error message returned by the underlying SDK, and contact Alibaba Cloud Technical Support to troubleshoot the issue.

-25

Unexpected error.

Record the full error message and verify the SDK initialization configuration.

-26

Invalid parameters for establishing a connection.

Ensure the initialization configuration is correct.

-27

The connection attempt timed out.

  1. Review the error message for details.

  2. Verify network connectivity.

-28

Failed to establish connection.

  1. Review the error message for details.

  2. Verify network connectivity.

-29

Connection endpoint does not exist.

1. The persistent connection endpoint cannot be resolved on the current network. 2. Verify network connectivity.

-30

Exception while establishing connection.

Review the error message for details.

-10000

Underlying network library information.

If the error code is less than -10000, add 10000 to get the corresponding underlying network library error code. To troubleshoot, refer to the documentation for the underlying network library's error codes.

Legacy error codes (V2.3.5 - V4.0.0)

Error name

Error code

Description

MISSING_PARAM

10101

A required parameter is missing. See the detailed error message to provide it.

INVALID_PARAM

10102

An invalid parameter was provided. See the detailed error message.

SIGN_NOT_MATCH

10103

The server signature does not match the client signature. Verify your AppKey and AppSecret.

TAG_ERROR

10104

A tag-related error occurred. See the detailed error message.

ALIAS_ERROR

10105

An alias-related error occurred. See the detailed error message.

INTERNAL_ERROR

10106

An internal server error occurred.

IO_ERROR

10107

A network I/O error occurred.

RESPONSE_PARSE_ERROR

10108

Failed to parse the response.

CONNECTION_FAIL

10109

The network connection failed. Check your network configuration.

SYSTEM_ERROR

10110

A system error occurred.

UNKNOWN_ERROR

10111

An unknown error occurred.

NO_NETWORK

10201

The network is unavailable.

APPKEY_NULL

10202

Invalid AppKey.

APPSECRET_NULL

10203

Invalid AppSecret.

APPRECEIVER_NULL

10204

The callback function is null.

REG_TIME_OUT

10205

Request timeout. For version 3.x and earlier, check the error-level logs with the awcn tag.

CONN_INVALID

10206

The current connection is invalid.

NO_CONNECTION

10207

No network connection. For version 3.x and earlier, check the error-level logs with the awcn tag. Ensure the corresponding .so package is added. For more information, see How to resolve error "1105, network unstable or connection exception"?

TAIR_ERROR

10209

A server error occurred.

INVALID_DEVICEID

10210

Invalid device ID.

INVALID_PACKAGE

10211

The package name does not match the configuration.

ACCS_CHANNEL_INIT_FAIL

10212

The silent connection process (the channel process by default) failed to initialize. For more information, see the second subsection under "A previously working integration suddenly fails" in Android Push Failure Troubleshooting Steps.

API_INVALID_INPUT

20101

Invalid parameters. See the detailed error message.

APP_VERSION_INVALID

20103

The app version parameter is invalid. Check your version number. The version number must not be null or longer than 32 characters.

CHANNEL_PROCESS_NULL

20105

ChannelService does not have a helper process configured.

REQUIRED_COMPONENT_NOT_EXISTS

20106

A required core component is not configured. See the detailed error message.

CONTINOUS_CRASH

20107

The system disabled the push service due to continuous crashes.

Common error codes (v2.3.4 and earlier)

Error parameter

Error code

NO_NETWORK

1101

REG_FAIL

1056

INVAILD_APPKEY

1052

INVAILD_PACKAGENAME

1053

INVAILD_APPSECRET

1054

NETWORK_UNSTABLE

1105

INVAILD_SERVER_RETURN

1115

SYSTEM_UNKNOWN_ERROR

1108