To further troubleshoot this issue, enable verbose logging and execute the app on a hardware device:

1. Edit your MceConfig.json in the project and ensure you have “loglevel”: “verbose” and “logfile”: true.
2. Delete the app from the test device, if present.
3. Build, execute the app, and recreate the scenario on the device.
4. Capture the full execution log (from Xcode console or logcat or extract the logfile itself from the device).
5. Finally, zip the execution log and the MceConfig.json and attach to your ticket.

If your device scenario can’t be recreated with the device connected to Xcode, you can extract verbose SDK logs from iOS development devices by:

1. Choosing menu item Xcode-> Windows-> Devices & Simulators.
2. Choose devices.
3. Installed app - choose your app.
4. Tap the gear icon and choose Download container.

The resulting container can be right-clicked, then Show Package Contents, and you can navigate to

1. “App Data -> Documents” for verbose SDK logs.
2. “Library -> {app bundle id}” for SDK sqlite DBs and plist settings.

If your device scenario can’t be recreated with the device connected to Android Studio, you can extract verbose SDK logs from Android development devices from the location /storage/self/Android/data/{app.bundle.id}/cache/ibm-mce-android-sdk/logs/ by using “adb pull /storage/self/Android/data/{app.bundle.id}/cache/ibm-mce-android-sdk/logs/ .” Your Android developer will understand how to use “ADB pull” to extract the files in our /logs directory.