BlackBerry Dynamics SDK for Android version 10.0 Skip Navigation

BlackBerry Dynamics SDK for Android
version 10.0

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

Changes to the SDK and software requirements
Feature
Description
Support for
Android
12
Android
12 is supported in this release.
BlackBerry Dynamics
apps can now target API level 31.
Integrate the SDK with a Maven repository
You can now use a remote Maven repository to integrate the SDK. It's a best practice to integrate the SDK using this new repository. For more information, see the Development Guide.
Removal of QUERY_ALL_PACKAGES permission
The QUERY_ALL_PACKAGES permission has been removed in this release. As a result, the
Protect Mobile
malware scanning and sideload detection features have been disabled. To include these features, developers must include the QUERY_ALL_PACKAGES permission in their
Android
manifest and request the required permission from
Google
when they submit their apps to the
Google Play
store.
Unsupported methods
Due to current data leakage prevention (DLP) controls, the setOnReceiveContentListener method is not supported in the following components and widgets:
  • com.good.gd.widget.GDAutoCompleteTextView
  • com.good.gd.widget.GDEditText
  • com.good.gd.widget.GDMultiAutoCompleteTextView
  • com.good.gd.widget.GDSearchView
  • com.good.gd.widget.GDTextView
  • com.good.gd.widget.GDWebView
  • com.blackberry.bbwebview.BBWebView
CURL upgrade
In this release CURL has been upgraded to version 7.77.0.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
version 3.3.0.215.

Fixed issues

The following issues are fixed in this release:
  • Error handling has been improved for QR code activation. (FIRST-17678)
  • If an administrator configured a
    BlackBerry Dynamics
    profile to require the
    UEM Client
    to serve as an authentication delegate for other
    BlackBerry Dynamics
    apps, the user would receive a notification explaining this requirement if they tried to activate a
    BlackBerry Dynamics
    app without having the
    UEM Client
    installed on their device. In this release, the same notification also displays if the
    UEM Client
    is installed but not activated. (GD-56528)

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. BlackBerry recommends using 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 is prompted to activate a
    BlackBerry Dynamics
    app using their password for another
    BlackBerry Dynamics
    app that they have previously activated (also known as Easy Activation), then cancels out of the prompt, the lock screen for the previously activated app displays instead of the screen to enter their activation credentials. (GD-56598)
  • If "Allow
    Android
    biometric authentication" is enabled in the
    BlackBerry Dynamics
    profile, when the user activates a
    BlackBerry Dynamics
    app on an
    Android
    12 emulator, fingerprint authentication fails for the app with the error message "Internal error: Retry or restart". (GD-56289)
  • If you configured the
    BlackBerry Dynamics
    profile to require users to enter their password when a
    BlackBerry Dynamics
    app returns to the foreground, on
    Android
    12 devices, this functionality does not work as expected (the app does not prompt the user for their password when it returns to the foreground). (GD-56162)
  • 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.