one-click logon SDK error codes-Phone Number Verification Service(PNVS)-阿里云帮助中心

This topic describes the error codes for the one-click logon software development kit (SDK).

Alibaba Cloud SDK return codes (H5 only)

Error code	Description	Cause and suggestion
600000	A success code is returned.	-
600004	The solution ID does not exist.	Confirm that you have created a solution ID in the Phone Number Verification Service console.
600010	An unknown exception occurred.	Possible causes: The `JwtToken` is invalid. A syntax error exists in the success callback. A network exception occurred.
600011	Failed to obtain the token.	Possible causes: The Wi-Fi switch was enabled during number acquisition. Browser settings, such as data-saving mode or network settings. For more information, see FAQ. Other causes. For more information, see Carrier error codes.
600013	The feature is unavailable due to carrier maintenance or upgrade.	Switch to another logon method and try again.
600014	The number of calls for this feature has reached the upper limit because of carrier maintenance or an upgrade.	Switch to another logon method and try again.
600015	API call timed out.	Try to log on using only the cellular network. You can also toggle airplane mode on and off, and then reopen the authorization page to check if the issue is resolved.
600018	The phone number is restricted by the carrier.	Contact the carrier to resolve this issue.
600025	The identity verification of the accessor failed.	Check whether a solution ID was created successfully.
600028	Invalid input parameters (`accessToken` or `jwtToken`).	Check whether the `accessToken` and `jwtToken` parameters are empty.
600030	Non-compliant CSS properties.	The title, protocol, and button cannot be empty. Check whether the related CSS properties are empty.
600032	Invalid business type.	This error code is returned in versions 2.1.6 and later. Check whether the `BizType` input parameter for the server-side `GetAuthToken` API is passed correctly.
600034	The request parameters have expired.	Call the server-side `GetAuthToken` API again to obtain a new authorization token.

Alibaba Cloud Phone Number Verification SDK return codes (HarmonyOS client only)

Return code	Return code descriptions	Recommended action
600000	Success.	-
600001	The authorization page was opened successfully.	-
600002	Failed to open the authorization page.	Reset the network. You can turn airplane mode on and then off. Alternatively, switch to another logon method, such as text message or WeChat logon.
600005	The device is insecure. For possible causes, see What are the causes for the "insecure device" error (600005)?	Switch to another logon method, such as text message or WeChat logon.
600007	No SIM card detected.	Check the SIM card and try again.
600008	Cellular network is not enabled.	Enable the cellular data network and try again.
600009	Cannot identify the carrier.	Check if the carrier is China Mobile, China Unicom, or China Telecom. Other carriers are not supported.
600010	Unknown exception.	Check if the SIM card status is normal, for example, check for overdue payments. You can also restart the cellular network and try again.
600011	Failed to get the token.	Check if the SIM card status is normal, for example, check for overdue payments. You can also restart the cellular network, restart the phone, or switch to another logon method and try again.
600012	Failed to get the token.	Check if the SIM card status is normal, for example, check for overdue payments. You can also restart the cellular network, restart the phone, or switch to another logon method and try again.
600015	Request timed out.	Try to log on using only cellular data. You can also toggle airplane mode (turn it on, then off) and then reopen the authorization page to test if it works.
600017	Failed to parse the key.	Make sure the project's package name, package signature, or AppId matches the key details in the Phone Number Verification Service console. Sync the correct key information to the API code.
600024	The device supports authentication.	-
600026	The authorization page already exists and cannot be opened again.	Check if you are calling the `preLogin` or `accelerateAuthPage` API after the authorization page is opened. This action is not allowed.
700000	Cancel User Authorization.	-
700002	The user clicked the logon button on the authorization page.	-
700003	The user clicked the protocol check box on the authorization page.	-
700008	The user clicked the confirm button in the secondary pop-up window.	-
700009	The user clicked the cancel button in the secondary pop-up window.	-

Alibaba Cloud SDK return codes (for app clients)

Error code	Description	Recommended action
600000	The token is successfully obtained.	-
600001	The authorization page is displayed.	-
600002	Failed to display the authorization page.	Reset the network. You can toggle airplane mode on and then off. You can also switch to another logon method, such as text message or WeChat.
600004	Failed to obtain carrier configuration information.	Upgrade the SDK to the latest version. You can download the latest SDK from the Phone Number Verification Service console.
600005	The mobile device is insecure. For information about possible causes, see Causes of the '600005: The mobile device is insecure' error.	Switch to another logon method, such as text message or WeChat.
600007	No SIM card is detected.	Check the SIM card and retry.
600008	The cellular data network is not enabled.	Enable the cellular data network and retry.
600009	The carrier cannot be identified.	Make sure that the carrier is China Mobile, China Unicom, or China Telecom. Other carriers are not supported.
600010	An unknown error occurred.	Check whether the SIM card is working as expected. For example, check whether the payment for the SIM card is overdue. You can also restart the cellular network and retry.
600011	Failed to obtain the token.	Check whether the SIM card is working as expected. For example, check whether the payment for the SIM card is overdue. You can also restart the cellular network, restart the mobile phone, or switch to another logon method.
600012	The number could not be pre-fetched.	Check the cellular data network and retry. You can also toggle airplane mode, restart the mobile phone, or switch to another logon method.
600013	The feature is unavailable because the carrier is performing maintenance or an upgrade.	Switch to another logon method.
600014	The call volume for this feature has reached the upper limit because the carrier is performing maintenance or an upgrade.	Switch to another logon method.
600015	The API call timed out.	Try to log on using only cellular data. You can also toggle airplane mode on and off and then display the authorization page again to check whether the issue is resolved.
600017	Failed to parse the package name, package signature, BundleID, or AppID of the client app, or the solution key does not match your app information.	Make sure that the app information in your project matches the key details of the solution in the Phone Number Verification Service console. We recommend that you perform the following checks: For Android, check whether the app signature has changed, or whether the solution key generated based on the app information is correctly synchronized to the code. For iOS, make sure that the BundleID of the app matches the key and that the correct key information is synchronized to the code.
600021	The carrier was switched when the user tapped Log on.	Switch to another logon method, such as text message or WeChat.
600023	An error occurred when loading custom controls.	Check whether the custom controls are added correctly.
600024	The device environment is ready for authentication.	-
600025	Invalid device check parameters.	Check whether the type and range of the input parameters are valid.
600026	The acceleration or pre-authentication API cannot be called after the authorization page is loaded.	Check whether the `preLogin` or `accelerateAuthPage` API is called after the authorization page is displayed. This behavior is not allowed.

Authorization page click event response codes (App client only)

Response code	Description
700000	The user clicked the back button and canceled the passwordless logon.
700001	The user clicked the switch button and canceled the passwordless logon.
700002	The logon button was clicked.
700003	The check box was clicked.
700004	The rich text of the protocol was clicked.
700006	The one-click logon button was clicked, which opened a secondary pop-up window on the authorization page.
700007	The secondary pop-up window for the privacy protocol was closed.
700008	The "Agree and Continue" button was clicked in the secondary pop-up window for the privacy protocol.
700009	The rich text of the protocol was clicked in the secondary pop-up window.
700010	The status code returned when the back button in the upper-left corner is clicked as the suspended page disappears (when suspendDisMissVC is set to YES).
700020	The authorization page was destroyed.

Carrier SDK error codes

China Mobile

Error code	Description	Recommended action
103000	Success.	-
500	Network exception.	Check the network settings.
503	Getting the token has ended.	Get the token again.
130010	A parameter is empty.	Check if the parameters are filled in.
105002	Failed to get the phone number from the China Mobile gateway.	Check if the network is available. Toggle airplane mode or restart the phone.
105112	Invalid timestamp.	Check if the timestamp is correct.
105113	The App ID is invalid or empty.	Check if the App ID is correct.
105312	Insufficient capability quota.	For a newly created solution ID, you must wait 15 to 30 minutes for China Mobile to sync the capabilities. An error is reported if the capabilities are not synced. An error is reported if the phone number has an overdue payment.
103101	Incorrect request signature.	Check if the solution configuration in the console is correct.
103134	The phone number obtained via WAP is empty.	-
110024	Incorrect BusinessType configuration.	Check the BusinessType configuration.
110023	The application has no permissions.	-
110025	The permissions have expired.	-
110026	Origin verification failed.	The request source registered on the open platform does not match the actual source. The origin ends with an extra "/".
103111	Incorrect WAP gateway IP address.	-
111002	The phone number is on the blacklist.	-
103609	Getting phone numbers from an Internet of Things (IoT) IP address is not allowed.	-
170001	Referer verification failed.	A cross-domain HTTPS request causes the Referer to be empty. For HTTPS access in a production environment, add the code to the head.
103211	Other errors.	-

China Unicom

Error code	Description	Recommended action
100	Success.	-
1101	Invalid public IP address.	The access request is not from valid data traffic. Check the public IP address.
1102	Invalid private IP address.	Information cannot be obtained using the private IP address. Restart the phone and try again.
1105	Invalid parameter information.	The SDK request parameters are abnormal.
1106	The application key information does not match.	The application parameter settings are abnormal.
1107	Insufficient balance.	Contact China Unicom for feedback.
1201	Failed to retrieve the number.	The SDK API request failed. Try again.
1203	Failed to obtain the authorization code.	Internal service query failed. Try again.
2101	Authentication failed.	SDK identity verification failed.
2201	Invalid APP ID.	The APP ID is inactive or invalid.
2202	Invalid application information.	The application information does not match the registered information.
2203	Invalid SDK information.	SDK information verification failed.
2205	Access information parsing error.	Failed to parse user information.
2206	The request throttling limit is exceeded.	The number of access requests exceeds the throttling limit.
3201	The system is busy.	An internal service exception occurred.
3202	Internal gateway error.	-
3203	Internal routing error.	-
3204	No payment permission.	-
3205	The number service is unavailable in this province.	-
3206	The ticket issuance feature is temporarily unavailable.	-
3207	This feature is not supported.	-
10100	No network connectivity.	The device is not connected to a network, or the current network connection is poor and unstable.
10101	The device is not connected to a cellular network.	The cellular network is not enabled on the device.
10102	The ApiKey cannot be empty.	A parameter passed to the initialization method is empty.
10103	Timeout.	The SDK API call timed out.
10106	A data decryption exception occurred.	The SDK failed to decrypt the data.
10109	General error.	A general or unknown error occurred.
20101	A maximum of 50 authorization codes can be obtained within 10 minutes.	The SDK performs local real-time request throttling.
30200	Invalid server-side data format.	The SDK cannot parse the API response.
-2	Invalid server-side data format.	The access request is not from valid data traffic.
410000	Request timed out.	Mobile networks are complex. A timeout error can occur if the timeout period is too short. To prevent timeout errors, we recommend that you set a timeout period. We recommend that you set the timeout period to more than 3 seconds.
410001	Failed to obtain the token.	Call the pre-fetch API first.
410002	An exception occurred when parsing the service response.	The data returned by the phone number retrieval service cannot be parsed.
410003	Failed to switch to the cellular network.	When both Wi-Fi and the cellular network are enabled, You cannot force phone number retrieval requests to use the cellular data network. Output.
410004	The cellular network is not enabled.	The cellular network is detected as disabled.
410005	A network detection exception occurred.	During the network provisioning check and the switching procedure The exception that was caught.
410007	Pre-fetched number has expired.	-
410010	The HTTP status code is 200 or 302. any other values.	-
410011	An exception was thrown during HTTPS communication.	-
410012	The status code is 200, but the response body is empty.	-
410013	Invalid redirect address.	-
410021	Initialization failed or operations are too frequent.	-
410024	An exception was thrown during HTTP communication.	-

China Telecom

Error code	Description	Recommended action
0	Request successful.	-
-64	Permission denied.	Check if the solution configuration in the console is correct.
-65	API-request-rates-Exceed-Limitations (API request rate limit exceeded).	Check if the network is available. You can toggle airplane mode, restart the phone, or switch to another logon method and try again.
100003	Request timed out.	Check if the network is available or try again later.
100004	Network unavailable.	Check if the network is available.
100005	The user clicked the back button in the navigation bar and did not complete the logon.	-
100009	Unknown error.	-
200001	Application authentication error (incorrect Client ID or Client Secret).	Check if the Client ID or Client Secret is correct.