Troubleshooting common issues

Problem

Possible solution

App crashes
  • A crash in the early stages of the app lifecycle is most likely caused by a configuration issue. Review the errors printed in the logs for details.
  • Initialize the BlackBerry Dynamics libraries before calling any other BlackBerry Dynamics API.

App crashes at startup

This can occur if android:maxSdkVersion is specified in the uses-permission element in AndroidManifest.xml (for example, <uses-permission android:maxSdkVersion="25" android:name="android.permission.WAKE_LOCK"/>). If a permission is defined with this syntax and the app is run on a device with an API level higher than the maxSdkVersion, the app is not granted the permission at startup and crashes.

Check the runtime merge process to identify and correct this issue.

Provisioning error

The email address or access key (PIN) has been incorrectly entered, or an old access key has been used. Double-check the credentials and, if necessary, send a new access key from the BlackBerry UEM management console.