Android SDK error codes

Android SDK Error Codes

For inner error codes, see Carrier Error Codes.

code	message	Remarks
1000	verify consistent	The phone number verification is consistent
1001	verify not consistent	The phone number verification is inconsistent
1002	unknown result	Unknown result
1003	token expired	Token expired
1004	sdk verify has been closed	SDK-initiated verification is not enabled
1005	Package name and AppKey do not match	Check whether the package name configured on the client is consistent with the package name configured for the corresponding AppKey application on the official website
1006	frequency of verifying single number is beyond the maximum limit	The verification consumption for the same number exceeds the limit within the natural day
1007	beyond daily frequency limit	The appKey verification consumption exceeds the limit within the natural day
1008	Invalid AppKey	Go to the official website to check the appkey in this application information and confirm that it is correct
1009	-	Go to the official website to check the application details; update the Jiguang SDK integrated in the application to the latest version
1010	verify interval is less than the minimum limit	The interval between two consecutive verification submissions for the same number is too short
1011	appSign invalid	Application signature error. Check whether the signature is consistent with the Portal settings
2000	Content is token	Token obtained successfully
2001	fetch token failed	Failed to obtain token
2002	init failed	SDK initialization failed
2003	network not reachable	Network connection is unavailable
2004	get uid failed	Jiguang service registration failed
2005	request timeout	Request timed out
2006	fetch config failed	Failed to obtain application configuration
2007	Content is exception information	A code exception occurred during verification
2008	Token requesting, please try again later	Token is being obtained. Try again later.
2009	verifying, please try again later	Verification is in progress. Try again later.
2010	don't have READ_PHONE_STATE permission	Permission to read phone status is not enabled
2011	Content is exception information	A code exception occurred while obtaining configuration
2012	Content is exception information	A code exception occurred while obtaining token
2013	Content is the specific error reason	A network exception occurred
2014	internal error while requesting token	An internal error occurred while requesting token
2016	network type not supported	The current network environment does not support verification
2017	carrier config invalid	Carrier configuration error
2018	Local unsupported operator	Locally unsupported carrier
3000	SMS verification code obtained successfully	SMS verification code obtained successfully
3001	Not initialized	Not initialized
3002	Invalid phone number	Invalid phone number
3003	Two requests are less than the configured interval apart	Two requests are less than the configured interval apart
3004	Unknown error	Request error. See the error message `msg` for details
4001	parameter invalid	Parameter error. Check parameters, such as whether the phone number format is incorrect
4014	appkey is blocked	The feature is disabled
4018	-	Insufficient balance
4031	-	Not a verification SDK user
4032	-	User configuration cannot be obtained
4033	appkey is not support login	Not a one-click login user. Configure the RSA public key in Verification Settings -> One-Click Login.
5000	bad server	Unknown server error
6000	Content is token	loginToken obtained successfully
6001	fetch loginToken failed	Failed to obtain loginToken
6002	fetch loginToken canceled	The user canceled obtaining loginToken
6003	UI resource loading exception	SDK-required resource files were not added correctly
6004	authorization requesting, please try again later	Login is in progress. Try again later.
6006	prelogin scrip expired.	The prefetch number result timed out and must be prefetched again
7000	preLogin success	SDK prefetch number succeeded
7001	preLogin failed	SDK prefetch number failed
7002	preLogin requesting, please try again later	Prefetching number. Try again later.
8000	init success	Initialization succeeded
8004	init failed	Initialization failed. See logs for details
8005	init timeout	Initialization timed out. Try again later.
-994	Network connection timed out	-
-996	Network connection disconnected	-
-997	Registration failed / login failed	Usually caused by no network. If the device network is normal but this issue persists, another possible reason is that the JPush server rejected registration. This is generally because the Android package name and AppKey of the current app are different from the Android package name and AppKey registered on Portal.