- What is the BlackBerry Dynamics SDK?
- Requirements and support for platform-specific features
- Steps to get started with the BlackBerry Dynamics SDK
- Integrating optional features
- Enforcing local compliance actions
- Adding custom policies for your app to the UEM management console
- Adding a custom logo and colors with the branding API
- Support for Night Mode
- Using zero sign-on for SaaS services through BlackBerry Enterprise Identity
- Integrating BlackBerry Enterprise Mobility Server services
- Creating wearable apps for Wear OS devices
- Implementing SafetyNet attestation for BlackBerry Dynamics apps
- Sample apps
- Testing and troubleshooting
- Implementing automated testing for BlackBerry Dynamics apps
- Automated testing with the BlackBerry Dynamics sample apps
- Preparing for automated testing
- Components of a sample automated testing configuration
- Execute all tests from the command line with Gradle
- Execute specific tests from the command line with Gradle
- Execute tests from the Android Studio IDE
- Add automated testing to your BlackBerry Dynamics Android app
- Configure compliance settings so you can debug your app
- Emulators and the rooted OS compliance setting
- Using enterprise simulation mode
- Troubleshooting common issues
- Logging and diagnostics
- Implementing automated testing for BlackBerry Dynamics apps
- Deploying your BlackBerry Dynamics app
- Deploying certificates to BlackBerry Dynamics apps
Troubleshooting common issues
Problem | Possible solution |
|---|---|
App crashes |
|
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. |