Skip Navigation

BlackBerry Dynamics SDK for Android
version 9.1

What's new in the
BlackBerry Dynamics SDK for Android
version 9.1

Changes to SDK and software requirements
Feature
Description
Changes to software requirements
Android
7 is no longer supported.
Voice over accessibility
BlackBerry Dynamics SDK for Android
now supports voice over accessibility for SDK screens.
Changes to user prompts for biometric authentication
Previously, if a user with a
Persona Mobile
entitlement was assigned a new
BlackBerry Dynamics
profile with a different configuration for biometric authentication (turned off in the original profile and enabled in the new profile, or enabled in the original profile and turned off in the new profile), a
BlackBerry Dynamics
app prompted the user every time the biometrics feature needed to be authorized and every time the feature was turned off.
In SDK version 9.1, a user with a
Persona Mobile
entitlement is prompted to authorize biometrics the first time the feature is enabled and is not prompted on subsequent changes of this setting. The previous authorization is saved and used if the feature is enabled again.
Background authorize support for
Android
GDAndroid.canAuthorizeAutonomously has been enhanced to allow
BlackBerry Dynamics
apps to background unlock, receive state callback, and use credential-protected storage.
The app can use canAuthorizeAutonomously() to check if it is possible to use background unlock, and if possible, authorize with serviceInit(). Two new GDAppEventType enum values have been added: GDAppEventBackgroundAuthorized and GDAppEventBackgroundNotAuthorized.
New administrative and security features
Feature
Description
Activate
BlackBerry Dynamics
apps using
BlackBerry Enterprise Identity
This SDK release and
UEM
12.14 add support for using
BlackBerry Enterprise Identity
to activate
BlackBerry Dynamics
apps. This supports the use of Active Directory, Ping Identity or Okta for activation through
Enterprise Identity
. For more information, see the BlackBerry Enterprise Identity content.
This featured is not supported for user accounts that were created using the legacy
Good Control
console or the legacy SOAP APIs.
Optional certificate enrollment
Previously, users could not access a
BlackBerry Dynamics
app unless they completed the certificate enrollment process. In
UEM
version 12.14, administrators can enable a setting in user credential profiles that allows users to dismiss certificate enrollment and complete it later.
For the Native Keystore connection type, the user is prompted to complete certificate enrollment each time the user starts the app. For the Entrust Smart Credential connection type, the app will not prompt the user again, but the user can complete certificate enrollment using the
UEM Client
.
Security enhancements
The SDK SecureStorage classes are now obfuscated.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
version 3.2.0.204.

Fixed issues

The following issues are fixed in this release:
  • If a user with the
    Android Enterprise
    activation type had One Lock enabled on the device, the user might have been prompted to import a PKI certificate each time they opened a
    BlackBerry Dynamics
    app. (FIRST-17434)

Known issues

  • If you use direct references to the
    BlackBerry Dynamics
    SDK .aar files in your build.gradle repositories (for example, compile(name:'android_handheld_platform-8.1.0.57', ext:'aar')) instead of using Maven linkage (for example, api "com.blackberry.blackberrydynamics:android_handheld_platform:8.1.0.57"), errors may occur in the AndroidManifest file in the
    Gradle
    caches directory. To resolve, use Maven linkage or specify android_handheld_resources and android_handheld_platform in the build.gradle file.
  • The
    Android
    certificate import API for the BlackBerry Dynamics SDK is no longer supported. It is recommended to use certificates from the
    Android
    Native Keystore if it is acceptable that the key material is protected by the device and not by
    BlackBerry Dynamics
    .
  • If a user with
    Android
    11 or later is activating a
    BlackBerry Dynamics
    app using a QR code and selects the "Only this time" option when prompted to grant permissions, certificate import issues might occur if the app remains in the background for longer than one minute during the import process.
    BlackBerry
    recommends that users select the "While using the app" option when prompted. (GD-54972)
    Workaround
    : Instruct users to force close the app and open it again.
  • If a
    BlackBerry Dynamics
    app uses
    Kerberos
    authentication and the app tries to access a web page using an IP address, after the user enters their credentials, the web page does not load as expected and the user is prompted for their credentials again in a loop. (GD-54481)
    Workaround
    : When developing
    BlackBerry Dynamics
    apps, do not hard code URLs that use IP addresses. If users can manually enter a URL, instruct users to avoid URLs that use an IP address.
  • If an app tries to open a
    BlackBerry Dynamics
    app that was not already open using AppKinetics, the
    BlackBerry Dynamics
    app might not come to the foreground. (GD-54205)
    Workaround
    : The user can start the
    BlackBerry Dynamics
    app and leave it running in the background before performing the AppKinetics operation.