This topic describes the error codes that are returned when you integrate the Fusion Authentication feature.
Alibaba Cloud SDK return codes
Error code | Description | Suggested action |
100001 | The specified scenario does not exist. | We recommend that you change the scenario ID. |
100002 | The continueSceneWithTemplateId method was called before the scenario started or before the node was complete. | Call the startSceneWithTemplateId method first or wait for the node flow to complete. |
100003 | The startSceneWithTemplateId or stopSceneWithTemplateId method was called before the node was complete, or the scenario ID does not match. | Wait for the node to complete or specify a valid scenario ID. |
100004 | The scenario has ended. | Call the stopSceneWithTemplateId method to end the flow. |
110005 | The scenario completed successfully. | - |
200001 | The next node could not be found. | This is the recommended detection template. |
200002 | The next node was found. | - |
200003 | The current node is not complete. Further operations are not allowed. | Wait for the current node to complete. |
300001 | Token authentication is in progress. | - |
300002 | The token is valid. | Wait for the token authentication to complete before you call the startSceneWithTemplateId method. |
300003 | The token is invalid. | We recommend replacing the token. |
300004 | The token request timed out. | Check the token retrieval method. |
300005 | The token failed to parse. | Check the token format. |
300006 | Token authentication failed. | Check the token format, scheme number, and other parameters. |
400003 | The one-click logon authorization page is displayed. | - |
400004 | The one-click logon authorization page failed to display. | Check the specific error message for details. |
400005 | Revoking One-click Logon Authorization. | - |
400006 | The token for one-click logon was obtained. | Use the token obtained in the onVerifySuccess callback to log on or switch accounts. Then, continue or end the flow based on the operation result. |
400007 | The token for one-click logon could not be obtained. | Check the specific error message for details. |
400008 | Click events for the one-click logon interface | - |
500001 | The text message verification code interface was initialized. | - |
500002 | The text message verification code interface failed to initialize. | Check the specific error message for details. |
500003 | The current logon phone number was obtained using Auto Fill. | Use the onGetPhoneNumberForVerific ation callback to pass the phone number. |
500004 | Auto Fill failed. | Check if the phone number format is valid. |
500005 | The text message verification code interface is displayed. | - |
500006 | The text message verification code interface failed to display. | Check if the interface is registered. |
500007 | The verification code was sent. | - |
500008 | The verification code failed to send. | Check the specific cause of the error. You can also continue or end the flow. |
500009 | Text message sending is throttled. | Adjust the throttling measures or wait for the limit to be lifted. You can also continue or end the flow. |
500010 | A risk was detected for the phone number when the text message was sent. | Continue or end the flow. |
500011 | The verification code was obtained and passed the phone number consistency check. | - |
500012 | The verification code that passed the phone number consistency check could not be obtained. | Check the specific error message in the onVerifyFailed callback for details. You can also continue or end the flow. |
500013 | The verification code was obtained. | - |
500014 | The verification code could not be obtained. | Check the specific error message in the onVerifyFailed callback for details. You can also continue or end the flow. |
500015 | The phone number failed the consistency check. | Check if the phone number passed in the onGetPhoneNumberForVerific ation callback is the same as the entered phone number. |
600001 | The uplink text message interface was initialized. | - |
600002 | The uplink text message interface failed to initialize. | Check the specific error message in the onVerifyFailed callback for details. You can also continue or end the flow. |
600003 | The uplink text message interface was created. | - |
600004 | The uplink text message interface failed to create. | Check if the interface is registered. |
600005 | The uplink text message was obtained. | - |
600006 | The destination number or verification code in the uplink text message is empty. | Enable logging and use getUpsmsMsg to filter. |
600007 | The uplink text message was obtained. | - |
600008 | The token for the uplink text message could not be obtained. | Enable logging and use getUpsmsMsg to filter. |
700001 | Risk detection was successful. | - |
700002 | Threat detection involves risks. | - |
700003 | Risk detection is throttled. | - |
700004 | Risk detection failed. | - |
900002 | The scheme number is empty. | Check the scheme number in the initWithToken method. |
900003 | The request to the Fusion Authentication API has started. | - |
900004 | The request to the Fusion Authentication API has ended. | - |
Click event response codes
Response code | Description |
410009 | The button to log on with another phone number is clicked on the one-click logon authorization page. |
410010 | The back button is clicked on the one-click logon authorization page. |
410011 | A protocol is clicked on the one-click logon authorization page. |
410011 | A protocol is clicked in the secondary pop-up window for one-click logon. |
510001 | The text message interface is canceled. |
510002 | The button to get a verification code is clicked on the text message interface. |
510003 | The button to submit the verification code is clicked on the text message interface. |
510004 | The back button is clicked on the text message interface. |
510005 | A protocol is checked in the logon or registration scenario on the text message interface. |
510006 | A protocol link is clicked to view the protocol in the logon or registration scenario on the text message interface. |
610001 | The uplink text message interface is canceled. |
610002 | The button to send a text message is clicked on the uplink interface. |
610003 | The "I have sent" button is clicked on the uplink interface. |
610003 | The back button is clicked on the uplink interface. |
One-click logon response codes
Response code | Description |
1600000 | The API call is successful. |
1600004 | Failed to obtain carrier configuration information. |
1600007 | No SIM card is detected. |
1600008 | The cellular network is disabled or unstable. |
1600009 | The carrier cannot be identified. |
1600010 | An unknown exception occurred. |
1600011 | Failed to obtain the token. |
1600012 | The number prefetch failed. |
1600013 | The carrier is performing maintenance and upgrades. This feature is unavailable. |
1600014 | The carrier is performing maintenance and upgrades. The maximum number of calls for this feature has been reached. |
1600015 | The API call timed out. |
1600017 | Failed to parse the AppID and Appkey. |
1600021 | The carrier has been switched. |
1600025 | Device environment detection failed. The device does not support authentication or the device detection parameters are incorrect. |
1600001 | The authorization page is displayed. |
1600002 | Failed to display the authorization page. |
1600026 | The acceleration or pre-fetch API cannot be called when the authorization page is loaded. |
1700000 | The back button is clicked. The user canceled one-click logon. |
1700001 | The switch button is clicked. The user canceled passwordless logon. |
1700002 | The logon button is clicked. |
1700003 | Checkbox click event. |
1700004 | The rich text of the protocol is clicked. |
1700006 | A secondary pop-up window is displayed for one-click logon. |
1700007 | The secondary pop-up window for the privacy protocol is closed. |
1700008 | The "Confirm and Continue" button is clicked in the secondary pop-up window for the privacy protocol. |
1700009 | The rich text of the protocol is clicked in the secondary pop-up window for the privacy protocol. |
Carrier SDK error codes
China Mobile
Error code | Description | Recommended action |
103000 | Success. | - |
500 | Network exception. | Check the network settings. |
503 | Getting token ended. | Get the token again. |
130010 | Parameter is empty. | Check if the parameter is filled in. |
105002 | Failed to retrieve the mobile gateway number. | 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 capacity. |
|
103101 | Incorrect request signature. | Check if the solution configuration in the console is correct. |
103134 | WAP phone number retrieval is empty. | - |
110024 | Incorrect BusinessType configuration. | Check the BusinessType configuration. |
110023 | The application has no rights. | - |
110025 | The rights 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 user's phone number is on the blacklist. | - |
103609 | Phone number retrieval is not allowed from an Internet of Things (IoT) IP address. | - |
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 retrieved using the private IP address. Restart the phone and try again. |
1105 | Invalid parameter information. | The SDK request parameters are invalid. |
1106 | The application key information does not match. | The application parameter configuration is invalid. |
1107 | Insufficient balance. | Contact China Unicom for assistance. |
1201 | Could not obtain a number. | The SDK API request failed. Try again. |
1203 | Failed to retrieve the credential code. | The internal service query failed. Try again. |
2101 | Authentication failed. | The SDK identity verification failed. |
2201 | Invalid App ID. | The App ID is not activated or is invalid. |
2202 | Invalid application information. | The application information does not match the registered information. |
2203 | Invalid SDK information. | The SDK information verification failed. |
2205 | Failed to parse the access information. | Failed to parse the user information. |
2206 | The request throttling limit is exceeded. | The number of 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 | Phone number retrieval is not supported in the current province. | - |
3206 | The number lookup 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 | No cellular network connection. | The cellular network of the device is disabled. |
10102 | The ApiKey cannot be empty. | The parameter that is passed to the initialization method is empty. |
10103 | Timeout. | The SDK API access 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 | You can obtain a maximum of 50 authorization codes within 10 minutes. | This is a local real-time request throttling rule of the SDK. |
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. We recommend that you set the timeout period to more than 3 seconds. |
410001 | Failed to retrieve the token. | Call the pre-fetch API before you call this API. |
410002 | A service response parsing exception occurred. | The data returned by the phone number retrieval server cannot be parsed. |
410003 | Cannot switch to the cellular network. | If both Wi-Fi and cellular data are enabled, the phone number retrieval request cannot be forced to be sent over the cellular network. |
410004 | The data network is disabled. | The cellular network is disabled. |
410005 | A network detection exception occurred. | An exception occurred during network status detection and switching. |
410007 | The pre-fetched number has expired | - |
410010 | The HTTP status code is not 200 or 302. | - |
410011 | An exception occurred 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 occurred 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. | Check if the network is available. You can try toggling airplane mode, restarting the phone, or switching to another logon method. |
100003 | Request timed out. | Check if the network is available or try again later. |
100004 | Network is 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. |