BlackBerry Dynamics SDK for Android version 11.0 Skip Navigation

BlackBerry Dynamics SDK for Android
version 11.0

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

Changes to the SDK and software requirements
Feature
Description
Android
13 readiness
This release adds support for devices using Android 13. Due to new intent filtering on Android 13, which impacts easy activation, authentication delegation, and inter-container communications (ICC), you must update
BlackBerry Dynamics SDK for Android
to version 11.0.
As a result of the new intent filtering, apps that target Android 13 (API level 33) will only be supported in the
BlackBerry Dynamics SDK for Android
11.1 release.
BBWebView enhancements
The following enhancements to BBWebView are new in this release of
BlackBerry Dynamics SDK for Android
:
  • The onReceivedBBError function which allows BBWebView to notify a developer about an error, has been implemented .
  • The BBWebResourceError class which holds information about an error, has been implemented.
  • If the administrator enables the DLP policy in
    UEM
    , users can not drag and drop text to, from, or within a BBWebView page.
Changes to
Android
Studio SDK Manager support
Support for downloading the SDK using
Android
Studio's SDK manager is deprecated and removed in this release. Developers must only use
Gradle
for integration.
Changes to OkHttp support
The following changes to OkHttp support are new in this release of
BlackBerry Dynamics SDK for Android
:
ClipboardManager enhancements
The clearPrimaryClip() function has been added to the ClipboardManager class in this release of
BlackBerry Dynamics SDK for Android
. For more information, see ClipboardManager in the BlackBerry Dynamics API reference.
Third-party IDP activation enhancements
Users can now activate a
BlackBerry Dynamics
app through a third-party IDP, such as
Active Directory
or
Okta
. Users can also sign in using their organizational credentials if they need to reset their app password or if their app has been locked. If this feature is enabled by an administrator, users will not need to request an unlock code through
UEM
self-service or from their administrator.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
version 3.5.0.234

Fixed issues

The following issues are fixed in this release:
  • An issue where multiple credential prompts would display when setting up a
    Kerberos
    authentication method type test, has been resolved. (GD-59074)
  • An issue where a Dynamics app would get stuck at the splash screen after activating the app using insecure
    Wi-Fi
    , and then switching to secure
    Wi-Fi
    , has been resolved. (GD-59015)
  • An issue where
    BlackBerry Work
    would get stuck on the lock screen in some occasions, has been resolved. (GD-58990)
  • An issue where the Compose Email icon was disabled after attaching photos to an email message and returning to the home screen, has been resolved. (GD-58576)

Known Limitations

  • If a user switches from a third-party keyboard to the system keyboard, in some deployment configurations, the application may take a minute to detect the change and remove the
    Custom Keyboards Restricted
    notification. (GD-57693)
    Workaround:
    By relaunching the app, the notification will be removed and the user will be able to use the system keyboard immediately.

Known Behavior

  • The
    Android
    runtime permission
    POST_NOTIFICATIONS
    is no longer required by
    BlackBerry Dynamics SDK for Android
    11.0. However, if permission has been requested by the app and granted by the user, mobile threat detections will be alerted via push notification. For apps still using
    BlackBerry Dynamics SDK
    10.2 or earlier, the end user will be prompted to grant this permission after upgrading to
    Android
    13.
  • If a user opens a
    BlackBerry Dynamics
    app on an insecure
    Wi-Fi
    network while the
    Unsafe Wi-Fi detected
    compliance action is enabled, they will receive a dialog stating that the application is blocked for this network. If the user opens the network settings on
    Android
    13, the network settings panel will be blank until the user taps the
    Settings
    button from the panel.

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)