The Android Link SDK may return the following error codes when a device connects to IoT Platform.
Common error codes
This topic covers Android Link SDK error codes only. For error codes in IoT Platform logs, see IoT Platform logs.
|
Error code |
Sub-error code |
Description |
Note |
|
1101100 |
None |
ERROR_SDK_ERROR |
An internal exception occurred during SDK initialization. |
|
1101101 |
None |
ERROR_SDK_INIT_ERROR |
An error occurred during SDK initialization. |
|
120 |
ERROR_PARAMS_DEVICEINFO_INVALID |
The ProductKey or DeviceName in the device certificate is empty during initialization. |
|
|
121 |
ERROR_PARAMS_DEVICE_SECRET_NULL |
The DeviceSecret (device secret) in the device certificate is empty during initialization. |
|
|
122 |
ERROR_PARAMS_SECURE_MODE_ITLS_WITH_PS_NULL |
The iTLS authentication mode is used, but the ProductSecret (product key) in the device certificate is empty. |
|
|
123 |
ERROR_STATE_LINKKIT_DEINITING |
DEINIT is not complete. Wait for DEINIT to complete before you initialize the SDK. |
|
|
-33 |
None |
MQTT_CONNECT_ERROR |
Failed to establish an MQTT connection.
|
|
-4 |
None |
ERROR_HTTP |
An error occurred when you called an HTTP API. For example, dynamic registration for a device that uses a unique certificate for each device failed.
|
|
1101220 |
None |
ERROR_COTA_GET_PARAMS_ERROR |
An error occurred in the request parameters for Remote Configuration. |
|
1101230 |
None |
ERROR_SHADOW_INVALID_STATE |
A device shadow API is called before the SDK is initialized. |
|
1101231 |
None |
ERROR_SHADOW_UPDATE_FAILED |
Failed to update the device shadow. For more information, see the error message. |
|
1101232 |
None |
ERROR_SHADOW_PARAMS_INVALID |
An error occurred in the parameters for updating the device shadow. |
|
1101312 |
None |
ERROR_GATEWAY_PERMIT_JOIN_DEVICE_INFO_INVALID |
The device information initialized when PermitJoin is called is invalid. |
|
1101300 |
None |
ERROR_GATEWAY_TOPO_NOT_ADDED |
The topology relationship is not added. |
|
1101301 |
None |
ERROR_GATEWAY_SUBDEV_NOT_LOGIN |
The sub-device is not logged on. |
|
1101302 |
None |
ERROR_GATEWAY_SUBDEV_WRAPPER_INFO_NULL |
The internal sub-device information in the SDK is empty. |
|
1101303 |
None |
ERROR_GATEWAY_SUBDEV_WRAPPER_NULL |
The internal sub-device does not exist in the SDK. |
|
1101304 |
None |
ERROR_GATEWAY_SUBDEV_THING_NOT_INITED |
The Thing Specification Language model for the sub-device is not initialized. |
|
1101305 |
None |
ERROR_GATEWAY_SUBDEV_LABEL_NULL |
Failed to obtain the sub-device tag. This usually occurs because the sub-device is not added before logon. |
|
1101306 |
None |
ERROR_GATEWAY_SUBDEV_SHADOW_NULL |
Failed to obtain the sub-device shadow. This usually occurs because the sub-device is not added before logon. |
|
1101307 |
None |
ERROR_GATEWAY_SUBDEV_COTA_NULL |
Failed to obtain the Remote Configuration for the sub-device. This usually occurs because the sub-device is not added before logon. |
|
1101308 |
None |
ERROR_GATEWAY_SUBDEV_INFO_INVALID |
The device certificate information of the sub-device is invalid. |
|
1101309 |
None |
ERROR_GATEWAY_SUBDEV_DISABLED |
The sub-device is disabled in the cloud. |
|
1101310 |
None |
ERROR_GATEWAY_SUBDEV_DELETED |
The sub-device is deleted. |
|
1101311 |
None |
ERROR_GATEWAY_LABEL_PARAMS_INVALID |
The request parameters for the tag are invalid. |
|
1101312 |
None |
LINKKIT_INIT_FAIL |
Initialization failed. This usually occurs because the MQTT connection is established, but is interrupted due to network issues during service initialization. This causes the overall initialization to fail. |
|
1101200 |
None |
ERROR_TMP_INIT |
Initialization failed. TMP initialization failed. |
|
1101201 |
None |
ERROR_DM_GET_TSL_INFO_INVALID |
Initialization failed. The obtained TSL information is invalid. |
|
1101202 |
None |
ERROR_DM_INIT_THING_PARAMS_INVALID |
Initialization failed. The parameters for obtaining the Thing Specification Language model are invalid. |
|
1101203 |
None |
ERROR_DM_GET_TMP_IDEVICE |
Initialization failed. Failed to obtain the Thing Specification Language model. |
|
1101204 |
None |
ERROR_DM_RESET_FAILED |
Failed to reset the device. For example, the MQTT connection is not established or is disconnected. |
|
1101205 |
None |
ERROR_DM_INIT_THING_FAILED_IS_INITING |
The Thing Specification Language model is initializing. |
|
1101020 |
None |
ERROR_DUPLICATE_SDK_INIT |
Duplicate initialization. The SDK is already initialized or is initializing. |
|
1102000 |
None |
ERROR_CALL_INTERFACE_PARAMS_ERROR |
An error occurred in the API call parameters. For more information about the API call, check the |
|
1102002 |
None |
ERROR_PARAMS_ERROR |
A parameter error occurred. |
|
200201 |
None |
DM_INIT_PARAMS_INVALID |
The initialization parameters are invalid. |
|
200301 |
None |
DM_INIT_GET_TSL_RESPONSE_ERROR |
Failed to obtain the Thing Specification Language model during initialization. |
|
100 |
None |
ERROR_DUPLICATE_SDK_INIT_DM |
The device management module is initialized more than once. |
|
101 |
None |
ERROR_DUPLICATE_SDK_INIT_LK |
The LinkKit SDK is initialized more than once. |
|
510 |
None |
ERROR_CMP_PARAMS_ERROR |
A CMP parameter error occurred. |
|
514 |
None |
ERROR_CMP_REGISTER_CONNECT_ERROR_EXIST |
The connection type is registered. You can ignore this error. |
|
517 |
None |
ERROR_CMP_SEND_ERROR_CONNECT_NOT_FOUND |
Failed to send the message. The current connection type does not exist. |
|
521 |
None |
ERROR_CMP_SEND_ERROR_CONNECT_NOT_CONNECTED |
Failed to send the message. The connection is not established. |
|
529 |
None |
ERROR_CMP_REGISTER_CONNECT_IS_REGISTERING |
The connection type is being registered. |
|
4201 |
None |
ERROR_UNKNOW |
An internal client error occurred. Call the |
|
4101 |
None |
ERROR_NETWORK_ERROR |
A network error occurred. For example, the network is unstable or the cell site signal is weak. |
|
4102 |
None |
ERROR_SERVER |
A service gateway error occurred. |
|
4103 |
None |
ERROR_BUSINESS |
|
MQTT error codes
The Android Link SDK uses the open-source Paho library for MQTT. The following table lists the native Paho error codes. If a connection is disconnected, check the error logs for the corresponding code.
1=Invalid protocol version
2=Invalid client ID
3=Agent program unavailable
4=Invalid username or password
5=Connection not authorized
6=Unexpected error
32000=Timed out while waiting for a response from the server
32100=Client connected
32101=Client disconnected
32102=Client is disconnecting
32103=Cannot connect to the server
32104=Client not connected
32105=The specified SocketFactory type does not match the agent program URI
32106=SSL configuration error
32107=Disconnecting using the callback method is not allowed
32108=Unrecognized package
32109=Disconnected
32110=Connection in progress
32111=Client closed
32200=Persistence is in use
32201=Token is in use
32202=Too many publications are in progress