Resolving Common Issues
If scanning the QR code or opening the deep link in Adobe Experience Platform Assurance does not open your app, deep linking may not be correctly configured in your mobile application.
Please follow OS developer documentation to learn more on setting up deep linking.
Android
iOS
When the generated link or QR code from Adobe Experience Platform Assurance is opened on device, it should launch your app and show a PIN screen to establish a Assurance session (as shown below). If this screen does not appear, ensure the following:

Connection error
Android
iOS
Java
public class MobileApp extends Application {
@Override
public void onCreate() {
super.onCreate();
MobileCore.setApplication(this);
MobileCore.configureWithAppId("yourAppId");
try {
Assurance.registerExtension();
MobileCore.start(null);
} catch (Exception e) {
// Log the exception
}
}
}
Swift
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
ACPCore.configure(withAppId: "yourAppId")
AEPAssurance.registerExtension() // <-- register AEPAssurance with Core
ACPCore.start(nil)
// Override point for customization after application launch.
return true;
}
The PIN screen may not show if the link or QR code is incorrect (or doesn't contain the query parameter
adb_validation_sessionid
). You may detect this error by seeing console logs with the following strings:Android
iOS
AdobeExperienceSDK: Assurance - Not a valid Assurance deeplink, Ignorning start session API call. URL : <deeplink URL>
AdobeExperienceSDK: Assurance - Not a valid Assurance deeplink, Ignorning start session API call. URL : <deeplink URL>
This issue may be resolved by scanning the right QR code or correctly copying the link generated in Assurance.
After you enter the PIN, if you see the following Connection Error:

Connection error
You may resolve it by double-checking the PIN is entered correctly from the session associated link or QR code:

Or ensuring internet connectivity on the device/simulator.
If you see a Invalid Launch & SDK Configuration error (see screenshot below), verify the following:
- 1.
- 2.
- 3.Ensure the device/simulator has internet connectivity

Invalid Launch & SDK configuration
Android
iOS
W/AdobeExperienceSDK: Assurance - Assurance connection closed. Reason: Invalid Configuration, Description: The Experience Cloud organization identifier is unavailable from the SDK. Ensure SDK configuration is setup correctly. See documentation for more detail.
[AdobeExperienceSDK ERROR <AEPAssurance>]: Invalid Configuration, Description: The Experience Cloud organization identifier is unavailable from the SDK. Ensure SDK configuration is setup correctly. See documentation for more detail.
This error may happen when you have access to multiple organizations in your Adobe Experience Cloud interface. To resolve, ensure the organization which houses the Experience Platform Launch mobile property is the same one as that where you are using Adobe Experience Platform Assurance.

Unauthorized access
Android
iOS
W/AdobeExperienceSDK: Assurance - Assurance connection closed. Reason: Unauthorized Access, Description: The Experience Cloud organization identifier does not match with that of the Assurance session. Ensure the right Experience Cloud organization is being used. See documentation for more detail.
[AdobeExperienceSDK ERROR <AEPAssurance>]: Assurance connection closed. Reason: Unauthorized Access, Description: The Experience Cloud organization identifier does not match with that of the Assurance session. Ensure the right Experience Cloud organization is being used. See documentation for more detail.
This SDK log message is not an error and is displayed during the routine course of SDK initialization. This message is expected if the app was not launched with an Adobe Experience Platform Assurance deep link. You may ignore this message if Assurance works as expected.
Android
iOS
D/AdobeExperienceSDK: Assurance - Timeout - Assurance did not receive deeplink to start Assurance session within 5 seconds. Shutting down Assurance extension
[AdobeExperienceSDK DEBUG <AEPAssurance>]: Timeout - Assurance extension did not receive session url. Shutting down from processing any further events.
This log message is not an error and will appear with routine usage on Android devices & simulators. You may ignore this log if Assurance works as expected.
W/AdobeExperienceSDK: Assurance - Failed to show fullscreen takeover, could not get fullScreenTakeover object.