- 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
- 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
- Integrating CylancePERSONA
- 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
FIPS-linking on Android
When you build an app, the
BlackBerry Dynamics SDK
links for FIPS compliance automatically. No special directives are required.To verify that FIPS has been included, verify that the following line is in the log output. This same line is printed at the start of the app launch:
IDeviceBase::initInstance: FIPS MODE REQUESTED
For information about logs, see Logging and diagnostics.
FIPS compliance is not supported on x86 emulators. If you want to test on x86 emulators, you must disable FIPS compliance.