Package-level declarations
Types
Error indicating trying to perform an operation for an account that is not enrolled in the SDK.
Error indicating that the necessary algorithm to be used for this operation is not available on this device.
Futurae authorization request failed.
Base generic error class for operations rejected by the API. This type indicates that an HTTP API request failed either with a specific error code from the server or by Network connectivity problems, reflected by the subtype of the error and httpCode and apiErrorCode.
Futurae internal server error
Error indicating that the SDK is in a corrupted state, such as missing necessary cryptographic material. Please call com.futurae.sdk.FuturaeSDK.reset to reset your SDK installation and continue or com.futurae.sdk.FuturaeSDK.launchAccountRecovery to recover accounts if the SDK's cryptopgraphic material is still present.
This is a recoverable error indicating that necessary SDK secrets are not found in storage. You can attempt to recover this state by launching the SDK via com.futurae.sdk.FuturaeSDK.launchAccountRecovery
Base generic error class for all SDK returned errors
Error indicating that an operation's input was invalid, such as a null SDK PIN while trying to unlock with SDK PIN.
Error indicating that an operation failed because operation inputs are in the wrong format.
Error indicating trying to perform an invalid operation, such as trying to lock/unlock SDK for an SDK configuration that doesn't support it or unlock with SDK PIN on a non-pin configuration.
Error indicating that the SDK operation encountered an invalid state.
Indicates that a secure operation was requested to be performed with the key that does not exist at the time of call.
Base generic error class for system Keystore errors. This type indicates that something went wrong while leveraging the system, such as trying to generate/use/delete a cryptographic key via Keystore or encrypting, decrypting or signing.
Error indicating that a Android Keystore operation failed, such as generating, deleting or using a cryptographic key.
Indicates that authenticating with the SDK failed.
Indicates that biometrics have been invalidated on this device
//TODO document
Indicates that the SDK configuration provided to initialize the SDK is invalid.
Error indicating that the system is unable to support requested operation, such as trying to enable biometrics without biometrics enrolled or trying to enforce a lock screen via SDK configuration without a lock screen set up on the phone.
Error indicating trying to perform a QR operation with an an unreadable or malformed QR code.
Indicates that the SDK failed to migrate a previous installation of SDK v1 to the format of SDK v2 (same for v3) Please call com.futurae.sdk.FuturaeSDK.reset to reset your SDK v1.x.x installation and continue with v2 or later
Exceptions related to com.futurae.sdk.FuturaeSDK.launchAccountRecovery
Indicates that @see com.futurae.sdk.FuturaeSDK.launchAccountRecovery has failed due to corrupted or missing cryptographic material and recovery is not possible.
Indicates that com.futurae.sdk.FuturaeSDK.launchAccountRecovery has failed a number of times and the SDK installation is no longer recoverable
Error indicating trying to perform an account related operation, while another account-related operation is running which blocks the SDK. You can use com.futurae.sdk.FuturaeSDK.sdkState to get notified about such blocking SDK states
Error indicating failure of cryptographic signature generation.
Error indicating trying to perform a protected operation without an unlocked SDK state.