SDK Errors

In this reference you can find a description of all errors that can occur in the Android SDK. See the error handling topic guide for more info on handling the errors when they occur.

Error Code Description
NETWORK_​CONNECTIVITY_​PROBLEM 9000 Due to a problem with the device internet connection it was not possible to initiate the requested action.
SERVER_​NOT_​REACHABLE 9001 It is not possible to connect with the Token Server.
DEVICE_DEREGISTERED 9002 The device registration was removed from the Token Server. All locally stored data is removed from the device and the user needs to register again.
USER_DEREGISTERED 9003 The user account is deregistered from the device. The user supplied the wrong PIN for too many times. All local data associated with the user profile has been removed.
OUTDATED_APP 9004 The Token Server denotes that the current app is no longer valid and can no longer be used. The end-user must update the application.
OUTDATED_OS 9005 The Token Server does not allow this application to run on the current OS version. Instruct the user to update the OS.
ACTION_CANCELED 9006 The action was cancelled.
DEVICE_​REGISTRATION_​ERROR 9008 The device could not be registered with the Token Server. Verify that the SDK configuration, Token Server configuration and security features are correctly configured.
USER_​NOT_​AUTHENTICATED 9010 The action can't be performed because no user is currently authenticated, possibly due to the fact that the access token has expired. A user must be authenticated in order to perform the action.
PIN_BLACKLISTED 9011 The provided PIN was marked as blacklisted on the Token Server.
PIN_IS_A_SEQUENCE 9012 The provided PIN contains a not allowed sequence.
PIN_​USES_​SIMILAR_​DIGITS 9013 The provided PIN contains too many similar digits.
WRONG_PIN_LENGTH 9014 The provided PIN length is invalid.
INVALID_​AUTHENTICATOR 9015 The authenticator that you tried to use is invalid. It may not exist, please verify whether you have supplied the correct authenticator.
DEVICE_​ALREADY_​ENROLLED 9016 The device is already enrolled for mobile authentication. This may happen in case an old push token is still left behind in the Token Server database and is reused by the OS.
ENROLLMENT_​NOT_​AVAILABLE 9017 The Mobile authentication feature is disabled in the Token Server configuration.
USER_​ALREADY_​ENROLLED 9018 The user is already enrolled for mobile authentication on another device.
USER_DISENROLLED 9020 The user has been disenrolled for mobile authentication.
MOBILE_​AUTHENTICATION_​NOT_​ENROLLED 9021 The user is not enrolled for mobile authentication.
AUTHENTICATOR_​DEREGISTERED 9022 Authentication with the custom authenticator has failed and the authenticator has been deregistered. Please check the CustomAuthenticatorInfo for details.
MOBILE_​AUTHENTICATION_​DISENROLLED 9023 The token has already been enrolled by other device. Mobile authentication with push has been disenrolled for all users on this device.
DATA_​STORAGE_​NOT_​AVAILABLE 9024 The data storage could not be accessed.
CUSTOM_​AUTHENTICATOR_​FAILURE 9027 Action with Custom authenticator has failed. Please check the CustomInfo for details.
ALREADY_HANDLED 9029 Requested mobile authentication request is already handled.
GENERAL_ERROR 10000 A generic error occurred.
CONFIGURATION_ERROR 10001 The Token Server configuration is invalid.
INVALID_STATE 10002 The SDK detected that there was a possible CSRF attack
LOCAL_​DEREGISTRATION 10003 The user was only deregistered on the device. The device registration has not been removed on the server-side due to a connection problem. This does not pose a problem but you might want to inform the end-user as he might be able to see that he/she is still registered through a web portal.
AUTHENTICATOR_​ALREADY_​REGISTERED 10004 The given authenticator is already registered and can therefore not be registered again.
FIDO_AUTHENTICATION_DISABLED (DEPRECATED) 10005 The Token Server configuration does not allow you to register FIDO authenticators. Enable FIDO authentication for the current application in the Token Server configuration to allow FIDO authenticator registration.
AUTHENTICATOR_​NOT_​SUPPORTED 10006 The given authenticator is not supported.
AUTHENTICATOR_​NOT_​REGISTERED 10007 The given authenticator is not registered.
AUTHENTICATOR_​PIN_​DEREGISTRATION_​NOT_​POSSIBLE 10008 The PIN authenticator can't be deregistered.
LOCAL_LOGOUT 10009 The user was only logged out on the device. The access token has not been invalidated on the server-side. This does not pose a problem but you might want to inform the end-user as he might be able to see that he/she is still logged in through a web portal.
DEVICE_​NOT_​AUTHENTICATED 10012 A device access token could not be retrieved. Check your Application configuration in the Token Server.
MOBILE_​AUTHENTICATION_​REQUEST_​NOT_​FOUND 10013 The mobile authentication request was not found. Please make sure that the mobile authentication request is available. This might be an indication that your Token Server setup is not complete. Cache replication might not work properly.
INVALID_REQUEST 10015 The request to the Token Server was invalid. Please verify that the Token Server configuration is correct and that no reverse proxy is interfering with the connection.
FIDO_SERVER_NOT_REACHABLE (DEPRECATED) 10016 The FIDO server is not reachable by the Token Server.
CUSTOM_​AUTHENTICATION_​DISABLED 10017 The Token Server configuration does not allow you to use custom authenticators. Enable custom authentication for the current application in the Token Server configuration to allow custom authenticator usage.
NOT_HANDLEABLE 10018 MobileAuth request cannot be handled by the SDK.
INVALID_​IDENTITY_​PROVIDER 10020 The specified Custom Identity Provider does not exist.
CUSTOM_​REGISTRATION_​EXPIRED 10021 Invalid transaction id/state.
CUSTOM_​REGISTRATION_​FAILURE 10022 Registration with the Custom Identity Provider has failed. Please check the CustomInfo for details.

Error map

We have compiled a matrix of SDK methods and errors. This provides an easy overview of which errors may occur in every SDK method. Unfortunately it is too big to show it on the current page. Hence you must click on the previous link to view this matrix.