Allegion Developer Portal

Android Mobile Access BLE SDK Error Codes and Resolution

Android
Platform Error Code Error Message Error Description Failure Reason Steps to Resolve
Android 100 GENERAL_ERROR The SDK was unable to instantiate a manager factory properly Payload manager has not yet been instantiated in BLE manager factory The SDK failed to retrieve the payload manager. This indicates that the SDK may not be properly initialized. Verify that the SDK initialization process has completed successfully before attempting any operations that rely on the payload manager. If the issue persists, consult the SDK documentation or contact Allegion support at developer.support@allegion.com.
Android 100 GENERAL_ERROR The SDK was unable to retrieve the account associated with this SDK instance An exception occurred while attempting account retrieval This error suggests that the account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 100 GENERAL_ERROR Failed due to lack of application context An application context was not provided to the SDK Make sure that the application context provided during SDK initialization is always correct to prevent errors
Android 101 OPERATION_FAILED A parameter format exception was thrown during a rights operation The SDK request used an invalid parameter Ensure you are passing the valid parameters, before invoking the SDK operation
Android 101 OPERATION_FAILED An invalid subscription key was used during the rights operation The SDK request used an invalid subscription key Ensure that valid tokens are supplied for SDK initialisation(Subscription key) and authentication(integration ID, ID token and access token). Additionally enable the SDK console logger for further details.
Android 101 OPERATION_FAILED An unregistered device was used during the rights operation The SDK request used an unregistered device This error signifies a failure in fetching rights. Ensure you call the authentication function before attempting to retrieve rights. During the first-time authentication operation, the device will be registered. Make sure your device is connected to the internet for this initial authentication.
Android 101 OPERATION_FAILED An invalid access right was used during the rights operation The SDK request used an invalid access right This error indicates that the provided RightID is not in valid format. Ensure the parameter with this request is valid and properly formatted
Android 101 OPERATION_FAILED An invalid header was used during the rights operation Access was denied due to invalid headers Confirm that the tokens(ID token and access token) are valid, unexpired, and properly signed. Refresh the tokens if necessary. Additionally, enable the console logger to view the HTTP requests and responses. Verify the header values to ensure that all fields are correctly set by the SDK.
Android 101 OPERATION_FAILED A server error occurred during the rights operation The SDK experienced a server error while attempting a rights request Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to perform the rights operation An exception occurred while attempting a rights operation This error indicates that the SDK is unable to retrieve the BLE access rights from the server. Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the BLE rights associated with this SDK instance An exception occurred while attempting rights retrieval from server This error indicates that the SDK is unable to retrieve the BLE access rights from the server. Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to complete the enrollment request An exception occurred while attempting to complete the enrollment request Ensure that you are using a valid subscription key and integration ID. These are provided by Allegion during the integration process. If you have any questions or require assistance regarding the subscription key/integration ID, please contact Allegion support at developer.support@allegion.com
Android 101 OPERATION_FAILED The SDK was unable to connect the requested account An exception occurred while attempting to connect the requested account This error signifies a failure in the 'create account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to retrieve a Connected Account stored with the SDK An exception occurred while attempting to retrieve a Connected Account This error signifies a failure in the 'create connected account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK encountered an error while attempting registration An exception occurred while attempting to register the device This error indicates a failure in the 'register device' network request. This request is initiated by the SDK during the first authentication on a device with network access. Ensure that your device is connected to the internet when performing the initial authentication.
Android 101 OPERATION_FAILED The SDK encountered an error while attempting account creation An exception occurred while attempting to create an account This error signifies a failure in the 'create account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to retrieve a Connected Account stored with the SDK An exception occurred while attempting to retrieve a Connected Account This error signifies a failure in the 'create connected account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED An invalid id token exception was thrown during an enrollment operation The SDK instance has an invalid id token This error indicates that the ID token provided for SDK authentication is invalid. Ensure that a valid ID token in the correct format is supplied during the SDK authentication process.
Android 101 OPERATION_FAILED Access was denied due to invalid subscription key during an enrollment operation This SDK instance requires an active subscription key Ensure that you are using a valid subscription key for SDK initialisation. The subscription key is provided by Allegion during the integration process. If you have any questions or require assistance regarding the subscription key, please contact Allegion support at developer.support@allegion.com
Android 101 OPERATION_FAILED An invalid encryption key exception was thrown during an enrollment operation This SDK instance requires a valid device encryption key Ensure you are using a proper context and your device supports secure storage
Android 101 OPERATION_FAILED An invalid integration id exception was thrown during an enrollment operation This SDK instance requires a valid integration id Please ensure that your integration has already been setup with allegion and verify that you are using a valid integration id.
Android 101 OPERATION_FAILED An account conflict was raised during an enrollment operation An account is already registered for this device This error signifies a failure in the 'create account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED An invalid header was used during the enrollment operation Access was denied due to invalid headers Confirm that the tokens(ID token and access token) are valid, unexpired, and properly signed. Refresh the tokens if necessary. Additionally, enable the console logger to view the HTTP requests and responses. Verify the header values to ensure that all fields are correctly set by the SDK.
Android 101 OPERATION_FAILED Request failed while attempting to contact the server The SDK instance was unable to contact the requested server Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to perform the enrollment operation An exception occurred while attempting an enrollment operation Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to initialize An attempt to initialize an already initialized SDK was made Ensure that the SDK is initialized only once per session, as multiple initializations within a single session are not valid.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the authentication manager The requested operation required the SDK instance to be initialized Make sure SDK is initialised before attempting the SDk authentication.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the rights manager The requested operation required the SDK instance to be initialized Make sure SDK is initialised before attempting the SDk authentication.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the rights manager The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the payload manager The requested operation required the SDK instance to be initialized The SDK failed to retrieve the payload manager. This indicates that the SDK may not be properly initialized. Verify that the SDK initialization process has completed successfully before attempting any operations that rely on the payload manager. If the issue persists, consult the SDK documentation or contact Allegion support at developer.support@allegion.com.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the payload manager The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the device search manager The requested operation required the SDK instance to be initialized The SDK failed to retrieve the device manager. This indicates that the SDK may not be properly initialized. Verify that the SDK initialization process has completed successfully before attempting any operations that rely on the payload manager. If the issue persists, consult the SDK documentation or contact Allegion support at developer.support@allegion.com.
Android 101 OPERATION_FAILED An error occurred while attempting to retrieve the device search manager The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the payloads associated with this SDK instance from the server An exception occurred while attempting payloads retrieval from server This error indicates that the SDK is unable to retrieve payload from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED A parameter format exception was thrown during a payload operation The SDK request used an invalid parameter Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED An invalid subscription key was used during the payloads operation The SDK request used an invalid subscription key Ensure that you are using a valid subscription key for SDK initialisation. The subscription key is provided by Allegion during the integration process. If you have any questions or require assistance regarding the subscription key, please contact Allegion support at developer.support@allegion.com
Android 101 OPERATION_FAILED An unregistered device was used during the payloads operation The SDK request used an unregistered device The Error indicates an unregistered device being used in the SDK request, please authenticate the device first, before attempting the SDK's requested operation
Android 101 OPERATION_FAILED An invalid access right was used during the payloads operation The SDK request used an invalid access right Ensure the parameter with this request is valid , before attempting the SDK's requested operation.
Android 101 OPERATION_FAILED An invalid header was used during the payloads operation Access was denied due to invalid headers This Error indicates invalid header was used during the payloads operation. Ensure that the header is valid before attempting the SDK's operation,
Android 101 OPERATION_FAILED A server error occurred during the payloads operation The SDK experienced a server error while attempting a payloads request Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to perform the payloads operation An exception occurred while attempting a payloads operation This error indicates that the SDK is unable to retrieve no-tour payload from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation No device was connected This Error no device was connected, Make sure Before initiating the disconnect operation, ensure the device is connected. Utilize the 'isConnected' method to verify the connection status.
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation An exception occurred while attempting to retrieve no tour payloads This error indicates that the SDK is unable to retrieve no-tour payload from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation An exception occurred while attempting to send the payload Ensure that SDK authentication is successfully completed. Additionally, verify that the mobile device's BLE capability is functioning correctly. If issues persist, try bringing the mobile device and the Allegion lock closer for better connectivity.
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation The requested operation required the SDK instance to be initialized Make sure SDK is initialised before attempting the SDk authentication.
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation The specified device is already connected Ensure that specified device is already connected. No additional connection attempts are required. Proceed with the intended operations
Android 101 OPERATION_FAILED The SDK was unable to perform a BLE device operation An exception occurred while attempting a BLE operation on the selected device Make sure SDK is authenticated before attempting the SDk operations.
Android 101 OPERATION_FAILED The SDK was unable to initialize an Account Manager An exception occurred while attempting to initialize the Account Manager The SDK failed to retrieve the account manager. This indicates that the SDK may not be properly initialized. Verify that the SDK initialization process has completed successfully before attempting any operations that rely on the account manager. If the issue persists, consult the SDK documentation or contact Allegion support at developer.support@allegion.com.
Android 101 OPERATION_FAILED The SDK was unable to confirm enrollment A failure occurred while attempting to confirm enrollment Make sure that network connectivity is maintained throughout the authentication process to successfully store enrolment data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 101 OPERATION_FAILED The SDK was unable to find the requested connected account An exception occurred while attempting to select a Connected Account This error suggests that the connected account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors, if the issue still persists, Please try clearing the app data. Steps to clear app data: 1. Locate and tap on the Settings app on your Android device. 2. Scroll down and find Apps, Applications, or App Management (the name may vary depending on the device and Android version). 3. From the list of installed apps, locate the app whose data you want to clear and tap on it. 4. Once you're in the app details, look for an option labeled Storage, Storage & Cache, or something similar, and tap on it. 5. You'll see two options: Clear Cache and Clear Data (or Manage Space on some devices). Tap on Clear Data. A confirmation message will appear, warning you that clearing data will reset the app to its default state (like when you first installed it). Confirm your action.
Android 101 OPERATION_FAILED The SDK was unable to Authenticate The requested operation required the SDK instance to be initialized Make sure SDK is initialized before attempting the SDk authentication.
Android 101 OPERATION_FAILED The SDK was unable to update the access token of a Connected Account The requested operation required the SDK instance to be initialized Make sure SDK is initialized before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to update the access token of a Connected Account The requested operation required the SDK instance to be authenticated Make sure SDK is authenticated before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to find the requested connected account An exception occurred while attempting to select a Connected Account Make sure SDK is initialised and authenticated before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to cancel an ongoing device search Unable to cancel search while there is not a search in progress The cancel scan function should only be used while the SDK is actively scanning. Check the SDK state before invoking this call
Android 101 OPERATION_FAILED The SDK was unable to search for devices The requested operation required the SDK instance to be initialized Make sure SDK is inialize before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to search for devices The requested operation required the SDK instance to be authenticated Make sure SDK is authenticated before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the access payloads associated with this SDK instance The requested operation required the SDK instance to be authenticated Make sure SDK is authenticated before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the access payloads associated with this SDK instance An exception occurred while attempting payloads retrieval from server This error indicates that the SDK is unable to retrieve access payload from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the access payloads associated with this SDK instance The requested operation required the SDK instance to be initialized Make sure SDK is inialize before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the access payloads associated with this SDK instance The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the BLE rights associated with this SDK instance The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the BLE rights associated with this SDK instance The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the BLE rights associated with this SDK instance An exception occurred while attempting rights retrieval from server This error indicates that the SDK is unable to retrieve BLE Rights from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 101 OPERATION_FAILED The SDK was unable to retrieve the BLE rights associated with this SDK instance The requested operation required the SDK instance to be initialized Make sure SDK is initialized before invoking any other SDK operations
Android 101 OPERATION_FAILED The SDK was unable to retrieve the BLE rights associated with this SDK instance The requested operation required the SDK instance to be authenticated Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
Android 200 CONNECTED_ACCOUNT_NOT_FOUND The SDK was unable to find the requested Connected Account No Connected Account could be found using the specified identifier Ensure that the ID token provided when invoking the authentication function is valid. This error suggests that the ID token being used is either invalid or expired. It may also occur due to issues with accessing secure storage. Check for any errors related to secure storage and ensure that the device is not rooted.
Android 201 UNABLE_TO_UPDATE_ACCESS_TOKEN The SDK was unable to update the access token of a Connected Account An exception occurred while attempting to update the access token of a Connected Account Verify the access token used while calling the authentication function is valid. This error indicates the access token used is invalid. The application is responsible for supplying a valid ID token and access token to the SDK.
Android 203 NO_CONNECTED_ACCOUNT_SELECTED The SDK was unable to update the access token of the currently selected connected account because there was no currently selected connected account The SDK currently does not have a connected account selected Ensure that the ID token provided when invoking the authentication function is valid. This error may also occur due to issues with reading from the secure storage. Verify if there are any secure storage-related errors and ensure that the device is not rooted.
Android 203 NO_CONNECTED_ACCOUNT_SELECTED The SDK was unable to retrieve a connected account while attempting to construct a Plenary Account A Connected Account must be attached to the SDK prior to Plenary Account retrieval Ensure SDK authentication is completed successfully to get a valid account and connected account id.
Android 204 ACCOUNT_NOT_FOUND The SDK was unable to retrieve the Plenary Account associated with this SDK instance The Account retrieved by the SDK was empty while attempting to construct a Plenary Account. No account has been stored with this SDK instance This error suggests that the account related information can not be retrieved from secure storage. This error may also occur due to issues with reading from the secure storage. Verify if there are any secure storage-related errors and ensure that the device is not rooted.
Android 206 TOKEN_MISSING_REQUIRED_CLAIM The SDK was unable to find the requested connected account The supplied ID token is missing a required claim Ensure you are passing the valid Id Token, before invoking the SDK operation
Android 207 INVALID_INTEGRATION_ID The SDK was supplied an invalid integration ID The supplied integration ID was missing or malformed This error indicates that the provided integration ID could not be parsed into a valid UUID format. Ensure that a properly formatted integration ID is supplied during SDK authentication. Ensure that you are using a valid integration ID. This provided by Allegion during the integration process. If you have any questions or require assistance regarding the integration ID, please contact Allegion support at developer.support@allegion.com
Android 207 INVALID_INTEGRATION_ID The SDK was not supplied with an integration ID The supplied ID token is missing a required claim Ensure that valid tokens are supplied for SDK initialisation(Subscription key) and authentication(integration ID, ID token and access token). Additionally enable the SDK console logger for further details.
Android 207 INVALID_INTEGRATION_ID he SDK was supplied an invalid integration ID The supplied ID token is missing a required claim Ensure that valid tokens are supplied for SDK initialisation(Subscription key) and authentication(integration ID, ID token and access token). Additionally enable the SDK console logger for further details.
Android 300 ILLEGAL_STATE The SDK was unable to transition to the desired state An exception occurred while attempting to transition to the desired state Verify the SDK's state before initiating any operations, and ensure that ongoing tasks are completed before attempting to trigger them again.
Android 301 SDK_NOT_INITIALIZED The SDK was unable to export an uncompressed public key The SDK was not configured during initialization Make sure SDK is inialize before invoking any other SDK methods.
Android 303 REQUESTED_OPERATION_IN_PROGRESS The SDK was unable to transition to the {desired} state An exception occurred while attempting to transition to the {desired} state Verify the SDK's state before initiating any operations, and ensure that ongoing tasks are completed before attempting to trigger them again.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested access payloads An exception occurred while attempting to store the requested access payloads This error suggests that the Payload related information can not be stored to Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested account An exception occurred while attempting to store the account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested connected account The SDK was unable to store the requested connected account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested account The SDK was unable to store the requested account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested BLE connected rights An exception occurred while attempting to store the requested BLE connected rights This error suggests that the BLE access right related information can not be stored to Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested connected accounts An exception occurred while attempting to store the requested connected accounts Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested no tour payloads An exception occurred while attempting to store the requested no tour payloads This error suggests that the no tour payload related information can not be stored to Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the specified model An exception occurred while attempting to store the specified model Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the updated access token An exception occurred while attempting to store the updated access token Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested account The SDK was unable to store the requested account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested account An exception occurred while attempting to store the account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested connected account An exception occurred while attempting to store the connected account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the result of enrollment An exception occurred while attempting to store the result of enrollment Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to complete Enrollment An exception occurred while attempting to store the result of enrollment Make sure that network connectivity is maintained throughout the authentication process to successfully store enrolment data in your phone's secure storage. Additionally, check for any secure storage-related errors and ensure that the device is not rooted.
Android 400 FAILED_TO_STORE_MODEL The SDK was unable to store the requested connected account An exception occurred while attempting to store the connected account Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken. if the issue still persists, Please try clearing the app data. Steps to clear app data: 1. Locate and tap on the Settings app on your Android device. 2. Scroll down and find Apps, Applications, or App Management (the name may vary depending on the device and Android version). 3. From the list of installed apps, locate the app whose data you want to clear and tap on it. 4. Once you're in the app details, look for an option labeled Storage, Storage & Cache, or something similar, and tap on it. 5. You'll see two options: Clear Cache and Clear Data (or Manage Space on some devices). Tap on Clear Data. A confirmation message will appear, warning you that clearing data will reset the app to its default state (like when you first installed it). Confirm your action.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the access payloads associated with this SDK instance An exception occurred while attempting access payload retrieval This error happens while trying to retrieve the Payload stored in the device. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the account associated with this SDK instance An exception occurred while attempting account retrieval This error suggests that the account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to initialize an instance of Account Persister The SDK was unable to retrieve the account associated with this SDK instance This error suggests that the connected account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors, if the issue still persists, Please try clearing the app data. Steps to clear app data: 1. Locate and tap on the Settings app on your Android device. 2. Scroll down and find Apps, Applications, or App Management (the name may vary depending on the device and Android version). 3. From the list of installed apps, locate the app whose data you want to clear and tap on it. 4. Once you're in the app details, look for an option labeled Storage, Storage & Cache, or something similar, and tap on it. 5. You'll see two options: Clear Cache and Clear Data (or Manage Space on some devices). Tap on Clear Data. A confirmation message will appear, warning you that clearing data will reset the app to its default state (like when you first installed it). Confirm your action.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to initialize an instance of Account Persister The SDK was unable to retrieve the connected accounts stored with the SDK This error suggests that the connected account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors, if the issue still persists, Please try clearing the app data. Steps to clear app data: 1. Locate and tap on the Settings app on your Android device. 2. Scroll down and find Apps, Applications, or App Management (the name may vary depending on the device and Android version). 3. From the list of installed apps, locate the app whose data you want to clear and tap on it. 4. Once you're in the app details, look for an option labeled Storage, Storage & Cache, or something similar, and tap on it. 5. You'll see two options: Clear Cache and Clear Data (or Manage Space on some devices). Tap on Clear Data. A confirmation message will appear, warning you that clearing data will reset the app to its default state (like when you first installed it). Confirm your action.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the BLE connected rights associated with this SDK instance An exception occurred while attempting BLE connected rights retrieval This error indicates that the SDK is unable to retrieve the BLE access rights from the server. Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the access payloads associated with this SDK instance An exception occurred while attempting access payload retrieval This error indicates that the SDK is unable to retrieve the payload from the server. Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the no tour payloads associated with this SDK instance An exception occurred while attempting no tour payload retrieval This error indicates that the SDK is unable to retrieve the BLE access rights from the server. Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the connected accounts stored with the SDK An exception occurred while attempting to retrieve a list of connected accounts This error happens while trying to retrieve the list of connected accounts stored in the device. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the no tour payloads associated with this SDK instance An exception occurred while attempting no tour payload retrieval This error happens while trying to retrieve the no tour payload stored in the device. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to retrieve the account associated with this SDK instance An exception occurred while attempting account retrieval This error happens while trying to retrieve the account stored in the device. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
Android 401 FAILED_TO_RETRIEVE_MODEL The SDK was unable to begin Authentication No Account credentials were found in persistent storage while attempting Authentication Ensure that a successful SDK authentication (with network access) has been completed and that the account data has been properly stored in the secure storage. Additionally, check for any secure storage-related errors and confirm that the device is not rooted.
Android 402 FAILED_TO_RETRIEVE_MODEL The SDK was unable to read a JWT token part after encoding it to BASE 64 The provided JWT token was malformed or improperly formatted This error indicates that the provided JWT token is not in the expected format. Please ensure that you supply a valid JWT token, structured correctly
Android 403 FAILED_TO_DESERIALIZE_MODEL The SDK was unable to parse a provided JWT token The provided JWT token was malformed or improperly formatted This error indicates that the provided JWT token is not in the expected format. Please ensure that you supply a valid JWT token, structured correctly
Android 403 FAILED_TO_DESERIALIZE_MODEL The SDK was unable to parse a provided JWT token The SDK was unable to convert a decoded JWT token part into JSON This error indicates that the provided JWT token is not in the expected format. Please ensure that you supply a valid JWT token, structured correctly
Android 403 FAILED_TO_DESERIALIZE_MODEL The SDK was unable to parse a provided JWT token An exception occurred while parsing the JWT claim This error indicates that the provided JWT token is not in the expected format. Please ensure that you supply a valid JWT token, structured correctly
Android 403 FAILED_TO_DESERIALIZE_MODEL The SDK was unable to parse a provided JWT token The provided JWT token had an improper number of elements This error indicates that the provided JWT token is not in the expected format. Please ensure that you supply a valid JWT token, structured correctly

iOS Mobile Access BLE SDK Error Codes and Resolution

iOS
Platform Error Code Error Message Error Description Failure Reason Steps to Resolve
iOS 1 errorDuringEnrollment An error occurred while trying to store an enrollment result. The requested operation result could not be stored. Make sure that network connectivity is maintained throughout the authentication process to successfully store enrolment data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
iOS 2 errorDuringCreateConnectedAccount An error occurred while trying to store a connected account. The requested operation result could not be stored. Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
iOS 3 errorDuringUpdateAccessToken Encountered an error while attempting to update the access token. Verify the access token used while calling the authentication function is valid. This error indicates the access token used is invalid. The application is responsible for supplying a valid ID token and access token to the SDK.
iOS 4 errorDuringSelectConnectedAccount An error occurred trying to select a connected account. Ensure that the access token provided when invoking the authentication function is valid. This error suggests that the access token being used is either invalid or expired. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 7 errorDuringAuthentication Unable to successfully complete authentication Unable to find account information for this device This error indicates that the saved account details could not be retrieved from the Keychain during local authentication. Ensure that a successful SDK authentication (with network access) has been completed and that the account data has been properly stored in the Keychain. Additionally, check for any Keychain-related errors and confirm that the device is not jailbroken.
iOS 9 errorDuringSendPayloads The attempt to send payloads to the device has failed. The SDK failed to send payloads to the device. Ensure that SDK authentication is successfully completed. Additionally, verify that the mobile device's BLE capability is functioning correctly. If issues persist, try bringing the mobile device and the Allegion lock closer for better connectivity.
iOS 100 invalidTransition Cannot start the requested operation as the operation is currently in progress The requested operation is already in progress. Verify the SDK's state before initiating any operations, and ensure that ongoing tasks are completed before attempting to trigger them again.
iOS 102 sdkNotInitialized SDK initialization required Authentication requires the SDK to be initialized. Make sure SDK is initialised before attempting the SDk authentication.
iOS 103 requestedOperationInProgress Cannot start the requested operation as the operation is currently in progress. The requested operation is already in progress. Verify the SDK's state before initiating any operations, and ensure that ongoing tasks are completed before attempting to trigger them again.
iOS 104 generalStateManagementError An unexpected error occurred while managing application state The state manager is unable to process the request Ensure that valid tokens(Subscription key) and authentication(integration ID, ID token and access token). Additionally enable the SDK console logger for further details.
iOS 105 sdkNotAuthenticated SDK authentication required The requested operation requires authentication Authentication of the SDK is mandatory at the beginning of each session. SDK methods are accessible only after successful authentication. Ensure that authentication is successfully completed using a valid token before invoking any other SDK methods.
iOS 106 sdkAlreadyInitialized SDK already initialized The SDK has already been initialized. Ensure that the SDK is initialized only once per session, as multiple initializations within a single session are not valid.
iOS 107 configurationError An error has occurred accessing the SDK Configuration The SDK Configuration is invalid or the subscription key is not set Ensure that a valid subscription key is provided when creating the MobileAccessConfiguration object, as it is required for SDK initialization.
iOS 108 deviceEncryptionKeyError The device encryption key is invalid The device may not support secure storage Ensure you are using a proper context and your device supports secure storage
iOS 109 sdkNotScanning The BLE scan could not be cancelled Canceling a BLE scan requires the SDK to currently be scanning The cancel scan function should only be used while the SDK is actively scanning. Check the SDK state before invoking this call
iOS 110 deviceAlreadyConnected The device is already connected Cannot connect to an already connected device Ensure the device is disconnected before attempting to reconnect. Refer to the SDK documentation for guidance on how to properly disconnect an Allegion lock device.
iOS 111 deviceNotConnected The operation requires the SDK be connected to the device The SDK is currently not connected to the device This error indicates that SDK functionalities requiring a BLE connection to the Allegion lock device are being attempted without a successful connection to the device. Ensure that the mobile device is properly connected to the Allegion lock before proceeding with this activity.
iOS 200 bleStartScanError The BLE scan could not be initiated Bluetooth usage is currently disabled, unsupported, or disallowed Ensure Bluetooth is enabled on your device and that the app has the necessary permissions. Also, check for any restrictions or policies that might block Bluetooth usage.
iOS 201 deviceConnectionTimeout The connection attempt timed out Connection was interrupted or the device is no longer in range Make sure there is at least one Allegion lock device within range. Try moving the lock and the mobile device closer together, then attempt to retry the connection.
iOS 202 devicePayloadTimeout The send payloads attempt timed out Sending payloads was interrupted or the device is no longer in range Make sure there is at least one Allegion lock device within range. Try moving the lock and the mobile device closer together, then attempt to resend the payloads.
iOS 300 jwtInvalidPartCount The supplied ID Token could not be parsed The supplied ID token does not contain the expected number of parts This error indicates that the provided ID token is not in valid format. Ensure that you supply a valid ID token in jwt format
iOS 301 jwtInvalidFormat The supplied ID Token could not be parsed The supplied ID token is not in the expected format This error indicates that the provided ID token is not in valid format. Ensure that you supply a valid ID token in jwt format
iOS 302 invalidIDToken The supplied ID Token could not be parsed Encountered an error while attempting to parse the ID Token This error indicates that the ID token provided for SDK authentication is invalid. Ensure that a valid ID token in the correct format is supplied during the SDK authentication process.
iOS 303 tokenMissingRequiredClaim The supplied ID token is missing a required claim The supplied ID token is missing a required claim This error indicates that the subject claim could not be parsed from the ID token provided during SDK authentication. Ensure that the ID token obtained from your identity provider includes all the required claims.
iOS 304 invalidIntegrationID The supplied integration ID was missing or malformed The supplied integration ID was invalid This error indicates that the provided integration ID could not be parsed into a valid UUID format. Ensure that a properly formatted integration ID is supplied during SDK authentication.
iOS 400 accountConflictServerError An account is already registered for this device An account cannot be created for an already registered device This error signifies a failure in the 'create account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
iOS 401 retrieveConnectedAccountServerError An unknown error occurred while attempting to retrieve a connected account The server request to retrieve the connected account failed This error signifies a failure in the 'create connected account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
iOS 402 accountConnectionServerError An unknown error occurred while attempting to connect your account The server request to connect the account failed This error signifies a failure in the 'create connected account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
iOS 403 accountCreationServerError An unknown error occurred while attempting to create an account The server request to create an account failed This error signifies a failure in the 'create account' network request. Ensure that your device is connected to the internet before performing SDK authentication for the first time. For further details, review the error code and description provided in the HTTP response.
iOS 404 deviceRegistrationServerError An unknown error occurred while attempting to register the device The server request to register the device failed This error indicates a failure in the 'register device' network request. This request is initiated by the SDK during the first authentication on a device with network access. Ensure that your device is connected to the internet when performing the initial authentication.
iOS 406 invalidIntegrationIDServerError The provided integration ID is invalid The server request failed due to an invalid integration ID Ensure that you are using a valid integration ID for SDK authentication. This integration ID is provided by Allegion during the integration process. If you have any questions or require assistance regarding the integration ID, please contact Allegion support at developer.support@allegion.com
iOS 407 invalidSubscriptionKeyServerError The provided subscription key is invalid The server request failed due to an invalid subscription key Ensure that you are using a valid subscription key for SDK initialisation. The subscription key is provided by Allegion during the integration process. If you have any questions or require assistance regarding the subscription key, please contact Allegion support at developer.support@allegion.com
iOS 408 invalidHeadersServerError The server denied access due to invalid headers The request to the server does not contain valid headers Confirm that the tokens(ID token and access token) are valid, unexpired, and properly signed. Refresh the tokens if necessary. Additionally, enable the console logger to view the HTTP requests and responses. Verify the header values to ensure that all fields are correctly set by the SDK.
iOS 409 unknownServerError An internal server error was returned from the server The server encountered an error Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
iOS 410 invalidAuthenticationServerError The server returned an error due to invalid authentication data The request to the server does not contain valid authentication data Ensure that you are using a valid subscription key and integration ID. These are provided by Allegion during the integration process. If you have any questions or require assistance regarding the subscription key/integration ID, please contact Allegion support at developer.support@allegion.com
iOS 700 failedToStoreAccount An error occurred while trying to store an account Account information may be lost or unavailable This error indicates that the account details could not be saved to the Keychain during SDK authentication. Make sure that network connectivity is maintained throughout the authentication process to successfully store account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
iOS 701 failedToStoreConnectedAccount An error occurred while trying to store a connected account Connected account information may be lost or unavailable This error indicates that the connected account details could not be saved to the Keychain during SDK authentication. Make sure that network connectivity is maintained throughout the authentication process to successfully store connected account-related data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
iOS 702 failedToStoreEnrollmentResult An error occurred while trying to store an enrollment result Connected account information may be lost or unavailable This error indicates that the enrolment result could not be saved to the Keychain during SDK authentication. Make sure that network connectivity is maintained throughout the authentication process to successfully store SDK enrolment data in your phone's secure storage. Additionally, check for any Keychain-related errors and ensure that the device is not jailbroken.
iOS 703 failedToUpdateAccessToken Encountered an error while attempting to update the access token No selected connected account was found Verify the access token used while calling the authentication function is valid. This error indicates the access token used is invalid. The application is responsible for supplying a valid ID token and access token to the SDK.
iOS 704 failedToRetrievePlenaryCredentials Encountered an error while attempting to update the access token No selected connected account was found This error suggests that the account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 705 failedToSelectConnectedAccount An error occurred trying to select a connected account Connected account information could not be retrieved from storage Ensure that the ID token provided when invoking the authentication function is valid. This error suggests that the ID token being used is either invalid or expired. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 707 failedToRetrieveAccount An error occurred while trying to retrieve an account from storage Account information could not be retrieved from storage This error suggests that the account related information can not be retrieved from Keychain. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 708 failedToRetrieveConnectedAccount An error occurred while trying to retrieve a connected account from storage Connected account information could not be retrieved from storage This error happens while trying to retrieve the list of connected accounts stored in the device. This error may also occur due to issues with reading from the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 709 failedToRemoveAccount An error occurred while trying to remove a connected account from storage Account information could not be removed from storage This error suggests that the account related information can not be removed from Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 710 failedToRemoveConnectedAccount An error occurred while trying to remove a connected account from storage Connected account information could not be removed from storage This issue happens while SDK trying to remove all connected accounts from the device. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 711 unknownDeviceStorageError Failed to access secure storage on the device This error suggests that the no-tour payload related information can not be removed from Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 712 failedToStoreBLERight An error occurred while trying to store a BLE right BLE right information may be lost or unavailable This error suggests that the BLE access right related information can not be stored to Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 713 failedToStoreAccessPayload An error occurred while trying to store an access payload Access payload information may be lost or unavailable This error suggests that the access payload can not be stored to Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken. Additionally make sure that internet connectivity was not interrupted during the authentication process.
iOS 714 failedToStoreNoTourPayload An error occurred while trying to store a no tour payload No tour payload information may be lost or unavailable This error suggests that the no-tour payload can not be stored to Keychain. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken. Additionally make sure that internet connectivity was not interrupted during the authentication process.
iOS 715 failedToRetrieveBLERight An error occurred while trying to retrieve a BLE right BLE right information could not be retrieved from storage This error indicates that the SDK is unable to retrieve the BLE access rights from the server. Ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
iOS 716 failedToRetrieveAccessPayload An error occurred while trying to retrieve an access payload Access payload information could not be retrieved from storage This error indicates that the SDK is unable to retrieve access payload from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
iOS 717 failedToRetrieveNoTourPayload An error occurred while trying to retrieve a no tour payload No tour payload information could not be retrieved from storage This error indicates that the SDK is unable to retrieve no-tour payload from the server. Ensure that you are passing a valid access token at the time of SDK authentication. Additionally, ensure that your device is connected to the internet before performing the task and network connectivity is maintained throughout the authentication process. For further details, review the error code and description provided in the HTTP response.
iOS 718 failedToRemoveBLERight An error occurred while trying to remove a BLE right BLE right information could not be removed from storage This issue happens while SDK trying to remove BLE access right from the device storage. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 719 failedToRemoveAccessPayload An error occurred while trying to remove an access payload Access payload information could not be removed from storage This issue happens while SDK trying to remove access payload from the device storage. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.
iOS 712 failedToRemoveNoTourPayload An error occurred while trying to remove a no tour payload No tour payload information could not be removed from storage This issue happens while SDK trying to remove no-tour payload from the device storage. This error can occur due to issues with reading from/writing to the Keychain. Verify if there are any Keychain-related errors and ensure that the device is not jailbroken.