Generic recommendations
The first SDK initialization requires active and stable Internet connection. After the first successful initialization, the SDK will cache essential settings, and following initializations will be much faster.
We recommend initializing the SDK in the background as soon as possible after app launch, to avoid any loading delays.
In case of an error during initialization, catch the error and continue the user flow. We recommend to treat this situation as if the user did not give consent. The next time the SDK is initialized correctly, you should collect consent normally.
The following sections explain what each error means.
Error: Unable to initialize due to poor or no network connection
This is typically caused by an unstable Internet connection on the first ever initialization. The SDK does not yet have the cached essential settings data available to be able to initialize offline.
It is possible to review / tweak the SDK initialisation options. The overview of the initialisation options can be found here: https://usercentrics.com/docs/apps/api/core-api/#usercentricsoptions
Error: Unable to initialize due to wrong configuration, please make sure your settingsID/ruleSetID is correct
This error is thrown when the Usercentrics SDK fails to find the settings ID or ruleset ID in our system. This is typically caused by:
an incorrect value in the settings ID or ruleset ID
entering both values at the same time
DNS / VPN issues caused by the end user's network
Error: Something went wrong during the initialization:
Any other issues that are not covered above.