| 1 |
Message Center Not Initialised |
The Mobile SDK could not enrol at the Message Center. Check that your Message Center is reachable and that the config string corresponds to the one you received from nextAuth for that Message Center URI. |
| 32 |
QR Parsing Error |
The QR code (or data from the deeplink uri) could not be parsed. |
| 33 |
QR Unknown Type |
The QR code (or data from the deeplink uri) does not have the expected type. |
| 34 |
No Accounts Found for Server |
The user scanned a login QR code (pointing to a specific server), but has no accounts in the Mobile SDK for that server. |
| 35 |
Display Name Already Exists |
The server forbids (in its server parameters) two accounts with the same display name to be registered by the Mobile SDK. The user already has an account with this server for the given display name in the Mobile SDK and can hence not register another. |
| 40 |
Single Account |
The Mobile SDK is configured to be used in a single account setup and does not allow for more than one account to be registered. Check that the Mobile SDK has no accounts. |
| 41 |
Enrol QR Expired |
The QR code for registration is no longer valid: it has either expired or was already used before to register an account. |
| 48 |
Server Authentication Failed |
Something went wrong while trying to authenticate the user at the nextAuth Server. Check that the account (for authenticating the user) still exists at the server. |
| 49 |
Server Authentication Error |
|
| 50 |
Server Authentication Timeout |
|
| 51 |
Server Authentication Unknown Error |
|
| 52 |
Server Not Allowed |
|
| 64 |
Server Parameters No Result |
After scanning a registration QR code, the Mobile SDK request server parameters at the nextAuth server. However, the nextAuth server could not find server parameters corresponding to this request. (older versions of the Mobile SDK also returned this error when the nextAuth server was not reachable) |
| 67 |
Server Parameters Parse Error |
|
| 68 |
Server Parameters Hash Incorrect |
The hash of the server parameters does not correspond to the hash included in the registration QR code. This can happen when the server parameters are updated after the registration QR code was generated. |
| 69 |
Server Parameters Invalid Signature |
|
| 70 |
Server Connection Error |
Could not connect to the nextAuth server. |
| 80 |
Push Decrypt Fail |
The received encrypted push message failed to decrypt. |
| 96 |
Second Factor No Valid Server |
The used Second Factor Server is not allowed by the nextAuth server. Check that the Second Factor Server corresponding to the app's config string is allowed in the nextAuth server for the (virtual) server at which the user is trying to authenticate. |
| 97 |
Second Factor Timestamp Failure |
There was too much time between the beginning of the second factor verification process (asking the user to provide his/her second factor) and the actual verification with the Second Factor Server. |
| 98 |
Cannot Set Biometric |
A biometric cannot be set since the current PIN is blocked (the process requires user confirmation by input of the current PIN). |
| 99 |
Cannot Change PIN |
The pin cannot be changed. |
| 100 |
User Input Required |
The mobile SDK is still waiting for user input and can currently not process your request (since handling your request will also require user input). |
| 101 |
Biometric Already Set |
Biometrics are already set. |
| 102 |
Biometric Not Set |
Biometrics are not set. |
| 256 |
Invalid/Unexpected Command |
|
| 257 |
Invalid Argument |
|