Android SDK Errors

Error Code	Error Message	Description
102	Invalid Certificate	Invalid Certificate, it might be expired or the device clock is out of sync
106	Missing algorithms	Indicates that `com.fireblocks.sdk.Fireblocks.generateMPCKeys` was called with an empty set of algorithms.
108	Incomplete device setup	Indicates that our device setup is incomplete. For example if we generated a key but we didn't perform backup
107	Missing private keys	The client failed to load the keys' content provided by the `com.fireblocks.sdk.keys.FireblocksKeyStorage` implementation. This implementation is provided to `com.fireblocks.sdk.Fireblocks` via the initialization method.
110	Invalid physical device id	Indicates that we have an invalid physical device id. Please check if your device was recovered from a different physical device
111	Max devices per wallet reached	The maximum number of devices in a wallet is reached while trying to add a new device.
200	Timeout during key creation, didn't get startup message	During key creation, several messages from the backend are handled. The first message did not arrive in the expected amount of time.
201	Unknown algorithm	Indicates that `com.fireblocks.sdk.Fireblocks.generateMPCKeys` was called with an invalid algorithm.
202	Failed to generate key, key exists in server but not on the device	The metadata of the key was previously sent to the backend, but the key is no longer on the client.
203	Timeout during key creation	During key creation, several messages from the backend are handled. One of the second-to-last messages did not arrive in the expected amount of time.
204	Failed to send public key	The public key failed to back up with the backend after key creation.
205	Failed to request key	One or more of the key requests failed to initiate.
206	Failed to enroll player	The process to register the `deviceId` with the backend failed.
207	Failed to create key	During key creation, several messages from the backend are handled. One of the messages failed to process on the device.
208	Failed to confirm key	Used in `com.fireblocks.sdk.Fireblocks.generateMPCKeys` during key creation, a key was not fully confirmed in the backend
300	Failed to request end-user takeover	A failure to receive keys for takeover from the backend.
301	Failed to takeover keys	There was an error while processing the takeover request on all keys.
302	Timeout during key takeover	A failure to receive keys for takeover from the backend in the expected amount of time.
400	Failed to export keys	The client failed to export all the available keys.
401	Missing public keys	Some of the data needed to export the key is unavailable.
402	Missing public key	The client failed to load the keys provided by the `com.fireblocks.sdk.keys.FireblocksKeyStorage` implementation. This implementation is provided to `com.fireblocks.sdk.Fireblocks` via the initialization method.
403	Failed to derive asset key	Deriving the asset key failed.
404	Missing cloud private keys	The cloud key share is not the full key share.
405	Missing chain code	The relevant chain code is missing.
406	Missing private key	The client failed to load the keys provided by the `com.fireblocks.sdk.keys.FireblocksKeyStorage` implementation. This implementation is provided to `com.fireblocks.sdk.Fireblocks` via the initialization method.
407	Failed to export key, recovered PublicKey is not equal to the original PublicKey	The recovered key is not equal to the original key.
408	Failed to export key	The key export failed. The reason for failure may be located in the logs.
500	Failed to sign transaction, unknown txId	Indicates that `com.fireblocks.sdk.Fireblocks.signTransaction` was called with an invalid transaction ID.
501	Error during transaction signing creation, didn't get start signing message	During transaction signing, several messages from the backend are handled. The first message failed to arrive in the expected amount of time.
502	Failed to sign transaction	The message processing failed.
503	Timeout during transaction signing	During transaction signing, several messages from the backend are handled. One of the second-to-last messages failed to arrive in the expected amount of time.
504	Transaction signing was stopped	Used in `com.fireblocks.sdk.Fireblocks.signTransaction` Indicates that the transaction signing was stopped
600	Backup not available	There are no keys to recover from the backend.
601	Failed to recover keys	The key recovery process failed.
603	Wrong passphrase	The provided passphrase is wrong
700	Failed to get key IDs	The client failed to fetch the key's metadata from the backend.
701	Missing key IDs in server for backup	The client failed to fetch the key's metadata from the backend.
702	We have a discrepancy between valid key IDs between server and client	A discrepancy exists between the `keyId` parameters stored on the client and the backend.
703	Failed to backup keys, missing keys	The client failed to fetch the key's metadata from the backend.
704	Failed to backup key	The key backup process with the backend failed.
705	Invalid passphrase error	The used passphrase is invalid.
800	Invalid add device setup data	The request to add a device failed due to invalid data.
900	Failed to join wallet	The request to join an existing wallet failed.
901	Timeout during join wallet	The request to join an existing wallet timed out.
902	Join wallet was stopped	The request to join an existing wallet was stopped.
1000	Failed to approve join wallet	The request to approve a new device joining an existing wallet failed.
1001	Timeout during approve join wallet	The request to approve a new device joining an existing wallet timed out.
1002	No keys to provision	Indicates that `com.fireblocks.sdk.Fireblocks.approveJoinWalletRequest` was called with an empty set of algorithms.
1003	Approve join wallet was stopped	The request to approve a new device joining an existing wallet was stopped.