- 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
- Implementing the BlackBerry Dynamics Launcher
- 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
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 13.0
- BlackBerry Dynamics SDK for Android Development Guide
- Requirements and support for platform-specific features
- Using an entitlement ID and version to uniquely identify a BlackBerry Dynamics app
Using an entitlement ID and version to uniquely identify a BlackBerry
Dynamics app
BlackBerry
Dynamics
appBlackBerry
Dynamics
apps are uniquely identified by a BlackBerry
Dynamics
entitlement ID (GDApplicationID) and entitlement version (GDApplicationVersion). The entitlement ID and entitlement version are used to manage end-user entitlement in the management console. The values are also used for app publishing and service provider registration.These values are specified in the assets/settings.json file for
Android
or in the Info.plist file for iOS
.You must define both the entitlement ID and the entitlement version for all of your
BlackBerry
Dynamics
apps, regardless of whether you use the Shared Services Framework. The same entitlement ID must be used to represent the app across all platforms.For more information about setting and checking the entitlement ID and version, the proper format to use for these values, and other requirements and considerations:
- See the GDAndroid Class reference in the BlackBerry Dynamics SDK for Android API Reference, especially these sections:
- Identification
- Indirect Authorization Initiation
- void authorize (GDAppEventListener eventListener ) throws GDInitializationError
- See the GDiOS Class reference in the BlackBerry Dynamics SDK for iOS API Reference, especially these sections:
- Identification
- Authorization
- - (void) authorize: (id< GDiOSDelegate > _Nonnull) delegate