Skip Navigation

BlackBerry Dynamics SDK for Android
version 10.1

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

Changes to the SDK and software requirements
Feature
Description
BlackBerry
WebView Library
The following changes have been made to
BlackBerry
WebView in this release:
  • Replaced any usage of com.blackberry.bbwebview.BBChromeClient with the new class name com.blackberry.bbwebview.BBWebChromeClient. This change has been made to better align with the naming of the native method.
  • The com.blackberry.bbwebview.WebClientObserver class is deprecated. For the required methods, you can extend BBWebViewClient, BBWebView, and BBWebChromeClient.  For more information about the methods to override in BBWebViewClient, BBWebView, or BBWebChromeClient, see the following Android developer resources:
  • BBWebView supports custom implementations of WebChromeClient and WebViewClient. To use this functionality, you must extend the BBWebChromeClient and BBWebViewClient classes.
  • HTTP authentication (Basic, Digest, NTLM,
    Kerberos
    ) is now supported in BBWebView. See Using the BBWebView library for more information.
Changes to API support
The OkHttp API is currently available as a beta feature release that is subject to further testing and changes.
The OkHttp API is now supported as a beta feature in this release. The support is provided from an Interceptor called BBCustomInterceptor, which when used will direct HTTP requests through the
BlackBerry Dynamics
communications system in the same way as the existing HttpClient API. See the BlackBerry Dynamics API guide for more information.
There are some limitations with OkHTTP in this release. See Limitations for OkHttp Support for more information.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
version 3.3.1.217.

Fixed issues

The following issues are fixed in this release:
  • A biometric authentication issue where the BlackBerry Dynamics app would crash if Android biometrics were enabled in UEM, but no biometrics were set up on the device, has been resolved. (FIRST-17729)
  • An issue where the BBWebView sample app binary XML would crash on startup has been resolved. (FIRST-17727)
  • An issue with caching criteria, which resulted in the wrong
    Kerberos
    ticket being sent in some cases, has been resolved. (FIRST-17590)
  • An issue where cancelling the Easy Activation process resulted in a redirection to the lock screen for the previously activated app has been resolved. The user will now be redirected to the app activation screen to enter their email address and access key. (GD-56598)

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.
  • If a user upgrades a
    BlackBerry Dynamics
    app that uses SDK version 9.x or earlier to a new version that uses SDK 10.1 or later, the app will not retain any cookies. (GD-55766)