Frequently asked questions
If you see SDK identifiers unexpectedly change, try the following fixes to address the issue. If none of these work, contact Customer Care at your earliest convenience for resolution:
- Ensure that no other versions of the SDK are running - for instance, if you are upgrading SDK versions from 4x to Experience Platform Mobile SDKs - remove all references to 4x SDKs. For 4x SDKs you may look (and remove) for the adobeMobileLibrary/AdobeMobile/AdobeMobileSDK dependency or lib in the project or if the verbose logs indicate ADBMobile prefixed entries.
- Examine app code for logic clearing app user defaults and/or shared preferences. SDK identifiers are stored in app user defaults and shared preferences and may not be cleared for proper functioning of the SDK.
- APIs such as setPrivacyStatus / resetIdentities clear SDK-stored identifiers - ensure that you are appropriately calling these APIs to avoid resetting SDK identifiers.
Crashesis computed based on the Lifecycle start and pause API calls implemented in your mobile application. How can you verify if the implementation is correct:
- Ensure that the Lifecycle extension is registered.
- Verify that both MobileCore APIs
lifecyclePauseare implemented in the application based on the recommended settings for each platform. See the guide for registering Lifecycle with MobileCore and adding appropriate start/pause calls.
A launch is measured by the SDK when a user opens the app for the first time or returns to the app after having been out of the app for longer than the specified timeout value. The typical timeout is 5 minutes (300 seconds) in the lifecycleTimeout configuration setting.
A visit is a server-side calculation by Adobe Analytics and is based on the first and last data hits that are sent by the SDK without exceeding a visit timeout. Typically, session timeouts are set at 30 minutes for a report suite. Although visits come from traditional web analytics, these hits still provide valuable insights into how users enter and exit from your app.
If you have followed the documentation and are unable to see reporting data in your Adobe Analytics dashboard, please consider the following next steps:
The Analytics extension and its dependent Identity extension should be registered and configured correctly for the SDK to start processing trackAction/trackState requests.
Ensure that your SDK timestamp configuration is aligned with the report suite's timestamp settings. That is,
analytics.offlineEnabledin the SDK configuration block for the Launch mobile property is aligned with the setting of Timestamp Configuration in your report suite. You may find Timestamp at Analytics > Admin > Report Suites > General > Timestamp Configuration.
The following settings explain how settings between the SDK and your report suite should be aligned:
analytics.offlineEnabled = trueties to timestamps required or optional
analytics.offlineEnabled = falseties to timestamps not allowed or optional
In the mobile property (tag) in the Data Collection UI, select the property from the list, then select Configure. If the "Privacy" setting is "Opted Out" the request is dropped by the SDK. If the setting is "Unknown" the request is queued on the device until the status changes to "Opted In" or "Opted Out". If these settings are managed in your app, navigate to the screen where the Privacy settings are updated with the SDK.
If you are unable to resolve your concerns through resources provided here, please contact Adobe Experience Cloud customer care for immediate assistance.
Last modified 5mo ago