- 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
- Add a watermark to the screens in a BlackBerry Dynamics app
- Using the BBWebView library
- Using the OkHttp HTTP framework
- Prompt the user to update a BlackBerry Dynamics app
- 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
- Integrating BlackBerry Analytics
- Implementing Play Integrity 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
Supported CPU architectures
The
BlackBerry Dynamics SDK
includes the native libraries built for the ARMv7, ARMv8, x86, and x86_64 CPU architectures. If you include the library project in your app, all of the ARMv7, ARMv8, x86, and x86_64 libraries are included when your app is built. Unless you use abiFilters
as described below, all library types will be included.Consider the following:
- Including multiple CPU architectures can increase the size of the app.
- x86 and x86_64 are supported forAndroidemulators as a faster alternative to ARM architectures. You may only want to include the x86 or x86_64 library in test versions of your app that you want to run on an emulator.
- Ensure that your app build includes the native library for each CPU architecture that it uses. It is a best practice to exclude native libraries for architectures that the app does not use. If the included libraries do not match the architecture used by the app, you may experience issues when running the app. For example, if your app uses a native library helloWorld_armv8.so, the app build must include the BlackBerry Dynamics ARMv8 library, and it does not need to include the ARMv7, x86, or x86_64 libraries.You can specify the required CPU architectures usingabiFiltersin the build.gradle file. For example, to include only ARMv7 libraries in your project:
defaultConfig { ndk { abiFilters "armeabi-v7a" } }