Android SDK error codes

Android SDK error code

JiGuang channel error code definition

Code	Description	Detailed explanation
-994	Network connection timeout	Try again later
-996	Network connection disconnected	If you ensure that the device network is normal, it may be because the package name is incorrect and the server forcibly disconnects the client
-997	Registration failed/login failed	(usually caused by the lack of network) If you ensure that the device network is normal and you still encounter this problem, there is another reason: the JPush server refuses to register. The reason for this is generally: the Android package name and AppKey of your current App are different from the Android package name and AppKey of the application you registered on the Portal
1005	Package name and AppKey do not match	Please check whether the package name configured on the client is consistent with the package name configured under the corresponding Appkey application on the official website
1008	AppKey is illegal	Please go to the official website to check the appkey in the application information and confirm it is correct
1009	No Android application has been created under the current appkey The SDK version you are using is lower than 1.8.2	Please go to the official website to check the application details of this application Update the JiGuang SDK integrated in the application to the latest
6001	Invalid setting	The old interface setting tag/alias/property before 3.0.7 should not have all parameters be null. The new tag/alias interface starting from 3.0.7 reports this error code to indicate that the tag/alias/property parameters cannot be empty
6002	Set timeout	It is recommended to try again, usually when the network is poor and initialization has not been completed
6003	alias string is illegal	Valid aliases and tags consist of: letters (case sensitive), numbers, underscores, Chinese characters, special characters (supported by 2.1.6)@!#$&*+=.\|
6004	alias is too long, up to 40 bytes	Chinese UTF-8 is 3 bytes
6005	A certain tag string is illegal	Valid aliases and tags consist of: letters (case sensitive), numbers, underscores, Chinese characters, special characters (supported by 2.1.6)@!#$&*+=.\|
6006	A certain tag is too long, a tag can be up to 40 bytes	Chinese UTF-8 is 3 bytes
6007	The number of tags exceeds the limit, up to 1000	This is a limit for one device. There is no limit to the number of global tags in an application
6008	tag exceeds total length limit	The maximum length of the new tag/alias interface in version 3.0.7 is up to 5000 bytes, and the total length of the old tag/alias interface is up to 7000 bytes
6009	Unknown error	Due to permission issues, PushService starts abnormally. There will be detailed error information in the client log, which can be checked accordingly
6011	Too frequent operations in a short period of time	Set tag/alias/property more than 10 times within 10s, or set mobile phone number more than 3 times within 10s
6012	The tag or alias or mobile phone number is set in the JPush service stop state	There is an error code added in version 3.0.0. After adjusting stopPush, you must call resumePush to restore the service before calling other APIs. Developers can perform relevant processing or prompts based on the information of this error code
6013	User device timeline abnormality	The error code added in version 3.0.6, abnormal changes in the local timeline of the device affect the setting frequency
6014	The server is busy, it is recommended to try again	New error codes in version 3.0.7
6015	appkey is in the blacklist	New in version 3.0.7, this appkey is in the blacklist, please contact support to remove it
6016	Invalid user	New error codes in version 3.0.7
6017	Invalid request	Error code added in version 3.0.7; new on 2020/03/10: The number of devices bound to the alias exceeds the limit, and a maximum of 10 devices are allowed to be bound. Please contact the business for more information
6018	Too many Tags	New in version 3.0.7, the number of tags set on this device exceeds 1,000. It is recommended to clear some tags first
6019	The query request has expired	New error codes in version 3.0.7
6020	tag/alias operation paused	There is a new error code in version 3.0.7, it is recommended to set it again after a while
6021	The tags operation is in progress, and other tags operations are temporarily unavailable	An error code added in version 3.0.7. If you call the tag-related API multiple times, please do the next operation after getting the callback of the last call; if the callback is not obtained, wait 20 seconds before doing the next operation
6022	The alias operation is in progress, and other alias operations are temporarily unavailable	An error code added in version 3.0.7. When calling the alias-related API multiple times, please do the next operation after getting the callback of the last call; if the callback is not obtained, wait 20 seconds before doing the next operation
6023	The mobile phone number is illegal	Error code added in version 3.1.1; it can only start with "+" or a number; the following content can only contain "-" and numbers
6024	Server internal error	New error code in version 3.1.1; server internal error, please try again after a while
6025	Mobile phone number is too long	An error code added in version 3.1.1; the mobile phone number is too long. The current maximum length of the mobile phone number detected by JiGuang is 20
6026	Data packet body is too large	An error code added in version 3.1.5; the data packet body is too large. Currently, the maximum data communication packet body supported by Jiguang is 8128
6027	The number of devices bound to the alias exceeds the limit	An error code added in version 3.5.8; Jiguang has limited the upper limit of "alias settings" on 2020/03/10, allowing up to 10 devices to be bound. If you need a higher limit, please contact the business
6036	Attribute operation permission restrictions	An error code added in version 4.8.0; this appkey has not enabled the user attribute function. If necessary, please contact the business operator
6037	Attribute operation parameter error	Please check whether the attribute parameter type format is correct; the attribute name should be of string type, and the attribute value only supports string, number, bool, and datetime types
6038	The last property request is still waiting for a response, and the next request cannot be executed for the time being	If you call the property-related API multiple times, please wait for 20 seconds before performing the next operation after obtaining the callback of the previous call. If the callback is not obtained, wait for 20 seconds before performing the next operation.