ATS Mobile SDK Error Codes

This article details all potential error codes users encounter while integrating with ATS Mobile SDK. View the list below to learn what each error code means and how to troubleshoot it.

Code	Label	Description	Troubleshooting Guide
100	`missingAppId`	A Config ID is not provided and SDK cannot initialize properly.	Check the initialize method of the `LRAts` SDK and verify that `configID` is provided. If initializing using the Google Mediation Adapter SDK, check if the configured adapter is executed with a Config ID in `appID`. To learn how to obtain Config ID, see "Implement ATS Mobile SDK".
101	`invalidAppId`	The provided Config ID is invalid and SDK cannot initialize properly.	Check the initialize method of the `LRAts` SDK and verify that the `configID` is valid. If initializing using the Google Mediation Adapter SDK , check if the configured adapter is executed with a valid Config ID in `appID`. To learn more about Config ID, see "Implement ATS Mobile SDK ".
102	`fetchingConfigurationFailed`	Configuration couldn’t be successfully retrieved for the specified `configID`.	Verify that the request for fetching configuration was successful. SDK will try to load cached configuration, if it’s also not available, an error will be returned.
103	`invalidConfiguration`	Configuration is not in the expected format.	Verify if the JSON response of the configuration request is in valid format. Names, properties, inner objects should be inline with data models inside the SDK. Check if the backend had a recent release and if a generation of configurations was impacted.
110	`sdkIsAlreadyLoading`	The SDK is already loading with different configuration.	Wait until `initialize` is finished before trying to initialize the SDK again.
111	`sdkIsAlreadyInitialized`	The SDK is already initialized with a different configuration.	To `initialize` the SDK with a different configuration, you must first call the `resetSdk` method and then initialize the SDK with a new configuration.
112	`sdkIsDisabled`	The SDK is in a `DISABLED` state.	You must first call the `isDisabled` method and set the `sdkDisabled` property to `false` to continue initializing the SDK.
113	`sdkIsNotReady`	The SDK is not fully initialized.	The SDK status must be `ready` before it can be used. Check if the SDK is properly initialized and that `getEnvelope`, `syncFilters`, and `getDealIDs` are called only after the initialization is completed.
120	`noConsent`	No consent is provided by user.	Check if the corresponding consent is present in `sharedPreferences` or `userDefaults`.
121	`noInternet`	No internet is detected.	Check if device has internet connection. Turn on airplane mode and turn it off or restart device.
122	`atsDisabledInCountry`	The device's corresponding country is not enabled in ATS placement.	Check if the user country is in the list of ATS-enabled countries. See "Configure ATS Placement" to view list of countries enabled for your ATS placement.
123	`databaseFailure`	Database couldn’t be opened.	SDK will try to restore itself. If it doesn’t help after reopening the app, reinstall it.
200	`sdkNotInitialized`	`getEnvelope` is called before the SDK is initialized.	Make sure the SDK is successfully initialized to get the envelope.
210	`emptyIdentifier`	`LRIdentifier` is not provided and the envelope can't be fetched.	Check the `getEnvelope` method of the `LRAts` SDK and verify that `LRIdentifier` is provided.
211	`invalidIdentifier`	The provided `LRIdentifier` is not valid and the envelope can’t be fetched.	Check the `getEnvelope` method of the `LRAts` SDK and verify that the `LRIdentifier` provided is in a valid format.
300	`fetchingEnvelopeFailed`	An error occurred while getting the envelope.	Check if the envelope request returned a successful response.Then, check if the cached envelope is expired, in which case the envelope cannot be refreshed or regenerated without an identifier.
301	`refreshingEnvelopeFailed`	Unable to refresh the envelope for an identifier.	Check if the request for refreshing envelopes was successful.
400	`syncDealsError`	Unable to sync bloom filters. Error occurred.	Check if bloom filters are available for specified configuration. If none of the specified bloom filters couldn’t be downloaded, verify that the server is available. Check the response of `/bloom-filters-mobile/bloom-filter-binary/` endpoint.