- What is the BlackBerry Dynamics SDK?
- BlackBerry Dynamics API reference
- Key features of the BlackBerry Dynamics SDK
- Activation
- Secure storage
- Secure communication
- Shared Services Framework
- Data Leakage Prevention
- User authentication
- Administrative controls
- Advanced security features with BlackBerry Protect Mobile
- Data collection and metrics with BlackBerry Analytics
- Dynamic security response with BlackBerry Persona
- 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
- 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 BlackBerry Persona
- 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
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 8.0
- BlackBerry Dynamics SDK for Android Development Guide
- Testing and troubleshooting
- Emulators and the rooted OS compliance setting
Emulators and the rooted OS compliance setting
If a compliance profile (
BlackBerry UEM
) or policy (standalone Good Control
) is configured to check for a rooted OS, and the profile or policy is applied to a BlackBerry
Dynamics
app that is running on a vanilla Android
emulator, the emulator will wipe the BlackBerry
Dynamics
app. The default behavior for the compliance setting is to wipe an app on a rooted device, and the emulator is considered a rooted device. Note that compliance actions related to SafetyNet
attestation and hardware certificate attestation will also consider an emulator to be compromised.This default compliance behavior is best for production service but interferes with development testing.
Consider any of the following recommendations for a development environment:
- Use enterprise simulation mode for basic operations on the emulator. This requires no setup in the management console. For more information, see Using enterprise simulation mode.
- Use a newAndroidemulator configuration with minimum API Level 26 that includes aGoogle Playsystem image. This configuration is not considered a rooted device.
- In the management console, configure and assign a new profile or policy set for development purposes, with the root detection setting disabled.