Errors
Type of the error | Error series X0000 | Description |
NFC Error | 1ХХХX | Errors in NFS Layer, e.g. Tag, connection and tranciesve errors. |
Encoding/Decoding error | 2ХХХX | Errors occured during the encoding or decoding data. |
Card Error | 3ХХХX | Errors from card SW codes |
Command Error | 4XXXX | Business logical errors that occurred inside commands' implmentation. |
SDK error | 5XXXX | Errors, that occurred in the apper level of SDK, like device restrictions, user canceled the operation or SDK is busy and can’t open the new session right now. |
All these errors should be handled by SDK. But if something will go wrong user will see the generic error text:
📢 An error occured during the operation
Code | Description |
10001 | Tag connection was lost |
10003 | Command is not supported |
10004 | Device is not supported |
10005 | NFC session is inactive |
10006 | Internal iOS NFC issue (NFC stuck) |
10007 | Session timeout |
10008 | Internal NFC Reader error |
📢 An error occured during the operation
Code | Description |
20001 | Error during APDU serialization. |
20002 | Error during APDU deserialization. |
20003 | TLV encoding failed due to type mismatch. |
20004 | TLV encoding failed. |
20005 | TLV decoding failed due to missing tag. |
20006 | TLV decoding failed due to type mismatch. |
20007 | TLV decoding failed. |
20008 | Failed to encrypt APDU. |
20009 | Failed to decrypt APDU. |
20010 | Failed to establish encryption. |
20011 | Invalid Response APDU. |
📢 An error occured during the operation
Code | Description |
30001 | Unknown result in response. This error mostly menans that device interrupted processing command and returned unknown error. Known devices: Nokia 8. |
30002 | Internal card error during processing command. (SW_ERROR_PROCESSING_COMMAND) |
30003 | Card state does not allow to run the command. (SW_INVALID_STATE) |
30004 | Card does not support this command. (SW_INS_NOT_SUPPOTED) |
30005 | Opration can't be completed due to invalid params. (SW_INVALID_PARAMS) |
30006 | APDU encryption is required by card. (SW_NEED_ENCRYPTION) |
30007 | File not found. (SW_FILE_NOT_FOUND) |
30008 | Wallet not found. (SW_WALLET_NOT_FOUND) |
Code | Message | Notes |
40101 | 📢 This card has already been personalized | Personalize command can't be performaed twice. Only for Dev cards. |
40001 | 📢 This card has not been personalized | Only for Dev cards. |
40002 | 📢 This card has not been activated | If activation flag is on, the card has to be activeted first. |
40003 | 📢 You cannot create a new wallet because this card has been purged | Deprecated error. Only for cards before 4.XX |
40004 | | This means that the card has not default PIN2 or CVC. SDK will ask user to input PIN2 or/and CVC and retry command. |
40501 | 📢 A wallet has already been created | You're trying to create wallet with the same index. |
40601 | 📢 Wallet cannot be purged | If wallet was created with isPermanent flag during card personalization. |
40801 | 📢 Access code cannot be changed | Access code can be set only if card.settings.isSettingAccessCodeAllowedistrue. |
40802 | 📢 Passcode cannot be changed | Passcode can be set only if card.settings.isSettingPasscodeAllowedistrue. |
40803 | 📢 Access Code cannot be changed to the default value. Please create a new code and try again. | |
40901 | 📢 You cannot sign data with this wallet because the card has reached its signature limit | Deprecated for cards since 4.0.0 |
40902 | 📢 There is nothing to sign here | |
40903 | | hashes' length in the array is not equal to each other |
40904 | 📢 Please create a wallet to sign data | |
40905 | 📢 This data cannot be signed | |
41106 | 📢 Data size exceeds the max limit of 32 Kbytes | |
40005 | 📢 Data verification is failed | |
40006 | 📢 Data size exceeds the max limit of 512 bytes | data.size > 512B |
40007 | 📢 The data cannot be written to the card because there is no counter. | |
40008 | | |
40009 | | |
40010 | 📢 Missing issuer public key | |
Last modified 1yr ago