Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Dynamics SDK for Android 11.2
  3. BlackBerry Dynamics SDK for Android Release Notes
  4. BlackBerry Dynamics SDK for Android version 11.2.0.13

BlackBerry Dynamics SDK for Android
 version 11.2.0.13

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

Changes to the SDK and software requirements:
Feature
Description
Support for
Play Integrity
 attestation
Play Integrity
 attestation is supported and added to the existing
SafetyNet
 attestation library. For more information, see Implementing Play Integrity attestation for BlackBerry Dynamics apps.
The
BlackBerry Dynamics SDK for Android
 11.2 is not compatible with previous versions of the
SafetyNet
 library.
BlackBerry Dynamics
 apps must use the latest
SafetyNet
 library distributed with the
BlackBerry Dynamics SDK for Android
 11.2 to support
Play Integrity
 attestation. For more information, see the BlackBerry Dynamics SDK for Android API reference.
Overlay detection support
You can now prevent a malicious overlay application from potentially observing a user's password entry by enabling "Prevent password entry if screen overlay detected on Android" in the
BlackBerry Dynamics
 profile in
UEM
.
The user will receive an alert if an overlay is detected, prompting them to close the application that is generating the overlay or revoke its permission to appear on top in the system preferences. Users will be prevented from entering their password and unlocking the application until the overlay is removed. This policy is turned off by default. For more information, see BlackBerry Dynamics profile settings in the
UEM
 documentation.
Enhancements to OkHttp support
You can now use the BBCustomInterceptor to upload files directly from
BlackBerry Dynamics
 file storage. For more information, see the BBCustomInterceptor Class Reference.
AppCompat widgets and automatic view class inflation
This release of the
BlackBerry Dynamics SDK for Android
 provides new AppCompat compatible widgets and a view class inflater to automatically inflate widgets, specified in layout files, into the correct
BlackBerry Dynamics
 widget classes. This avoids the need to recode all of the layout files for your app in order to take advantage of
BlackBerry Dynamics
' data leakage prevention capability. For more information, see the com.good.gd.widget API documentation.
Enhancements to BBWebView support
The following APIs and classes have been added to BBWebView to enhance authentication capability:
  • BBWebView.setAuthenticationPreferences(): This method allows you to set the authentication preferences for a BBWebView instance.
  • BBWebView.getAuthenticationPreferences(): This method allows you to get the authentication preferences for a BBWebView instance if they are available.
  • BBHttpAuthHandler.getAuthScheme(): This method allows you to get the authentication scheme information for an HTTP authentication.
  • com.blackberry.bbwebview.BBAuthScheme: This enum class allows you to get the authentication scheme constants for an HTTP authentication.
For more information, see the BBWebView API documentation.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
 version 3.6.0.251

Fixed issues

When unlocking a
BlackBerry Dynamics
 app with fingerprint authentication, the app would accept the fingerprint, but would still request a password before the app would unlock. (GD-61281)
BlackBerry Dynamics
 apps would crash during authentication while the device was in idle mode and the "Allow Biometrics" profile setting was enabled. (GD-60523)

Known Limitations

On
Samsung
 devices with
Android
 10, when a user copies color formatted text and pastes it into a non-GDTextView (android.widget.TextView) field, while the DLP policy "Do not allow copying data from non
BlackBerry Dynamics
 apps into
BlackBerry Dynamics
 apps" is turned off, the text will not maintain the color format. (GD-60975)
Users cannot upload files from
Google Drive
 by selecting the file from the native
Android
 file picker. (GD-60021)

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 is prompted to grant this permission after they upgrade to
Android
 13. (GD-58740)
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. (GD-59357)

Known issues

Play Integrity
 attestation will fail during app provision on an
Android
 emulator. (GD-61278)
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, 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 you use direct references to the
BlackBerry Dynamics
 SDK .aar files in your build.gradle repositories (for example,
implementation name:'android_handheld_platform-$DYNAMICS_SDK_VERSION', ext:'aar'
) instead of using Maven linkage (for example,
implementation 'com.blackberry.blackberrydynamics:android_handheld_platform:$DYNAMICS_SDK_VERSION'
), errors may occur in the AndroidManifest file in the
Gradle
 caches directory. To resolve this, use Maven linkage or specify
android_handheld_resources
 and
android_handheld_platform
 in the build.gradle file. (GD-51938)
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
. (GD-51742)