- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for client certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- BlackBerry Dynamics software versions
- Requirements
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Supported launchModes
- Compatibility with the BlackBerry Dynamics Launcher Library
- Supported CPU architectures
- Supported and unsupported Android and third-party features
- FIPS-linking on Android: automatic
- Restricted key prefix
- Steps to get started with the BlackBerry Dynamics SDK
- Installing the BlackBerry Dynamics SDK for Android
- Integrating the BlackBerry Dynamics SDK in .aar format
- Using the branding API to add a custom logo and colors
- Info: Add Samsung Pass to your BlackBerry Dynamics app
- Info: APIs for secure clipboard management
- Info: Preventing autobackup to Google Drive
- Info: APIs for network status
- BlackBerry Dynamics SDK for Android: Wearable Framework
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps
- Testing and troubleshooting
- Readying your app for deployment: server setup
- Details of support for client certificates
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 4.2
- BlackBerry Dynamics SDK for Android Development Guide
- Testing and troubleshooting
- Emulators and the rooted OS compliance policy
Emulators and the rooted OS compliance policy
If the
BlackBerry
Dynamics
compliance policy to check for a rooted OS 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 behaviour for the compliance policy in BlackBerry UEM
and in
standalone Good Control
is to wipe an
app on a rooted device, and the emulator is considered a rooted device.This default behaviour is best for production service but interferes with
development testing.
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 policy set for development purposes with the root detection policy disabled.