Error Codes
Error Codes for SDK v3.2.1 and Later
Important: Starting with Android Search Module v3.2.1, the response codes returned by the search callback interface have changed. See the table below for details.
When using asynchronous methods to search for information, the callback interface returns a response code. The response codes are listed below:
New Response Code | Status Description | Troubleshooting Strategy |
1000 | Request successful | Service call successful, results returned. |
1001 | Developer signature verification failed | 1. The developer enabled the "Digital Signature" feature in the Key console, but did not generate the "Digital Signature" using the specified algorithm. This currently occurs with Web service API and smart hardware positioning Keys. |
1002 | User Key is incorrect or expired | 1. Current website products only support Keys applied for after September 23, 2014. 2. Configure the feature according to the developer guide and verify the Key is added correctly. |
1003 | No permission to use the corresponding API | The developer does not have permission to use the corresponding service. For example, if a developer applies for a Key for web positioning and uses it to access the reverse geocoding API, this error is returned, and vice versa. |
1008 | MD5 security code verification failed | Check whether the SHA1 and package name are correct. |
1009 | Request Key does not match the bound platform | The Key used in the request does not match the bound platform. For example, the developer applied for a JS API Key but used it to call the Android SDK API. |
1012 | Insufficient permissions, service request denied | If you applied for an Android platform SDK, verify that the Key call is working correctly. If you have any issues, please provide feedback through the ticket system. |
1013 | The Key has been deleted | Check the console to see if the Key was accidentally deleted. |
1100 | Engine service response error | Please provide the error details through the ticket system. |
1101 | Engine returned abnormal data | Please provide feedback through the ticket system. |
1102 | AMAP server request connection timed out | Please provide feedback through the ticket system. |
1103 | Reading service result returned timed out | Please provide feedback through the ticket system. |
1200 | Invalid request parameter | Check whether the values of your request parameters comply with the specification. For example, if a parameter's value range is [1,3], the developer passed '4'. |
1201 | Missing required parameter in request | Check whether any required parameters are missing from your request. |
1202 | Invalid service request protocol | Invalid service request protocol. |
1203 | Unknown server error | Please provide feedback through the ticket system. |
1800 | New server error | If you have any issues, please provide feedback through the ticket system. |
1801 | Protocol parsing error | Protocol parsing error. |
1802 | Socket connection timed out - SocketTimeoutException | First, check whether the network connection is stable. |
1803 | URL exception - MalformedURLException | This is a Java exception. The probability of this occurring in the SDK is extremely low. |
1804 | Unknown host - UnknownHostException | Check whether the network connection is stable. |
1806 | HTTP or socket connection failed - ConnectionException | Check the network status and stability. |
1900 | Unknown error | SDK local error code. Please provide feedback through the ticket system. |
1901 | Invalid parameter | Check whether the parameter settings are correct. |
1902 | IO operation exception - IOException | SDK local error code. Please provide feedback through the ticket system. |
1903 | Null pointer exception - NullPointerException | SDK local error code. Please provide feedback through the ticket system. |
2000 | Incorrect table ID format | Check your table ID in the Cloud Map Data Management Console. |
2001 | Data ID does not exist | A data ID in the cloud map data table does not exist. Check in the Cloud Map Data Management Console. |
2002 | Cloud search server is under maintenance | Please provide feedback through the ticket system. |
2003 | Table ID corresponding to the Key does not exist | Check whether the table ID exists. |
2100 | User ID not found | Check whether the user ID for the Nearby feature exists. |
2101 | App Key has not enabled the "Nearby" feature | |
2200 | Clearing the table or enabling single-point upload while auto-upload is enabled | Check your code logic for this scenario. |
2201 | Invalid USERID | Check whether the UserID is empty, contains invalid characters, exceeds 32 characters, or is different from the previously uploaded UserID. |
2202 | NearbyInfo object is empty | Check whether the NearbyInfo object is empty. |
2203 | Interval between two single uploads is less than 7 seconds | The interval between two single uploads is less than 7 seconds. |
2204 | Point is empty or identical to the previously uploaded point | The Point is empty or identical to the previously uploaded point. |
3000 | Planning points (including origin, destination, and waypoints) are outside mainland China | This issue may occur when using the route planning service API. The planning points (including origin, destination, and waypoints) are outside mainland China. |
3001 | No road found near the planning points (including origin, destination, and waypoints) | This issue may occur when using the route planning service API. No road was found near the planning points (origin, destination, and waypoints). |
3002 | Route calculation failed, usually due to road connectivity issues | This issue may occur when using the route planning service API. Route calculation failed, usually due to road connectivity issues. |
3003 | Walking route calculation failed because the distance between the origin and destination is too long | |
4000 | Short link sharing authentication failed | If you have any issues, please provide feedback through the ticket system. |
4001 | Short link request failed | If you have any issues, please provide feedback through the ticket system. |
Error Codes for SDK Versions Earlier than v3.2.1
When using asynchronous methods to search for information, the callback interface returns a response code. The response codes are listed below:
Response Code | Description |
0 | Normal, results returned. |
13 | User ID not found. Check whether the provided user ID exists. |
16 | App Key has not enabled the "Nearby" feature. Please register a Nearby Key. |
21 | IO operation exception. |
22 | Connection exception. Check whether the network is stable. |
23 | Connection timed out. |
24 | Invalid parameter. |
25 | Null pointer exception. |
26 | URL exception. |
27 | Unknown host. |
28 | Failed to connect to the server. |
29 | Communication protocol parsing error. |
30 | HTTP connection failed. |
31 | Server exception. |
32 | Key authentication verification failed. Check whether the SHA1 value and package name bound to the Key match the APK. |
33 | Service returned information failed. |
34 | Service is under maintenance. Please try again later. |
35 | The number of requests from the current IP has exceeded the quota. |
36 | Request parameter error. Adjust the parameters according to the developer guide. |
1001 | Signature error. |
1901 | Short link sharing authentication failed. |
2000 | The table ID for the search does not exist. Check whether it is configured. |
2001 | The ID for the search does not exist. Check whether the input is correct. |