Skip to main content
Version: 5.0

VaultErrorCodes

The meaning of the error code in the thrown VaultError.

Enumeration members

AndroidBiometricsLockedOut

Biometrics have been locked out, usually because of too many failed attempts.

Note: This error will never be thrown if using DeviceSecurityType.SystemPasscode or DeviceSecurityType.Both. Its currently not possible to get the nature of failures from the native authentication dialog, so the only error that would be thrown is VaultErrorCodes.UserCanceledInteraction as the user is forced to cancel the prompt.

Constant

17

AndroidSystemPasscodeUnavailable

DeviceSecurityType.SystemPasscode for DeviceSecurityType not available on this Android device.

Constant

16

AndroidUnexpectedKeystoreError

An unexpected error has occurred in the Android keystore.

Constant

19

AuthFailed

User authentication failed.

Constant

6

BiometricsNotEnabled

The operation failed because biometric authentication is not enabled. This can occur when biometrics is not supported by the device or when biometrics has not been configured for the device or vault.

Constant

13

InvalidArguments

The operation failed because the some of the vault provided arguments were invalid.

Constant

3

InvalidatedCredential

The credentials were invalidated. This can happen when a user changes biometrics or passcode.

Constant

4

KeyNotFound

The key was not found. This can happen when a user changes biometrics or passcode.

Constant

12

MismatchedPasscode

The user provided mismatched passcodes.

Constant

9

MissingBiometrics

Biometrics have not been authed yet (Android only)

Constant

15

MissingPasscode

The operation requires passcode to be setup but it isn't set yet. Call Vault.setCustomPasscode to set it.

Constant

10

PasscodeNotEnabled

The operation failed because the application tried to unlock the vault with passcode authentication, but the vault is not configured to allow passcode authentication.

Constant

11

SecurityNotAvailable

Biometric security is unavailable due to a passcode not being set up at the system level. In order to use biometric identification on the device a system level passcode must be set up by the user.

Constant

5

TooManyFailedAttempts

Too many failed authentication attempts made against the custom passcode vault, so the vault was cleared and user will need to login again.

Constant

7

Unknown

An unknown error happened.

Constant

0

UserCanceledInteraction

The user cancelled the native authentication dialog.

Note: On iOS, this error code will also be thrown in the event that the native authentication dialog fails as a result of too many failed attempts. The user will be forced to cancel the dialog, triggering this error code.

On Android, this error also will be thrown if using DeviceSecurityType.SystemPasscode or DeviceSecurityType.Both in the event of too many failed attempts. Its currently not possible to get the nature of failures from the native authentication dialog, and similar to iOS, the user will be forced to cancel the dialog, triggering this error code.

Constant

8

VaultLocked

The operation failed because the vault was locked.

Constant

1

VaultUnavailable

The operation failed because the vault was unavailable. The most likely cause of this error is that a vault has not been configured.

Constant

2

iOSBiometricsLockedOut

Biometrics have been locked out, usually because of too many failed attempts.

Constant

18