BlackBerry Dynamics SDK for Android version 12.1.1.43
BlackBerry Dynamics SDK for Android
version 12.1.1.43What's new in the BlackBerry Dynamics SDK for Android version 12.1.1.43
BlackBerry Dynamics SDK for Android
version 12.1.1.43Changes to the SDK and software requirements:
Feature | Description |
|---|---|
Support for WebSockets | WebSockets are now supported in the BBWebView library. For more information, see Using the BBWebView library. |
Enhancement to BBWebView | The HTML data retrieved using the loadDataWithBaseURL method now supports data leakage prevention controls for cut, copy, and paste. |
Changes to Android compatibility | The BlackBerry Dynamics SDK for Android is no longer compatible with Android 10 (API 29). |
Changes to Java compatibility | Java 17 or later is now required for development with the BlackBerry Dynamics SDK for Android . |
Deprecation of BlackBerry Persona compatibility | The BlackBerry Dynamics SDK for Android is no longer compatible with BlackBerry Persona . APIs related to BlackBerry Persona , such as BISThreatStatusAPI, have been removed. |
BlackBerry Dynamics Launcher Library
BlackBerry Dynamics Launcher Library
This release uses
BlackBerry Dynamics Launcher Library
version 12.1.590.4Fixed issues
If a BlackBerry
Dynamics app was sent to the background and then returned to the foreground, UI issues might have occured on the password screen. (GD-62273, GD-62380) |
In some instances, the cancel button did not display on the certificate enrollment screen. (GD-62302) |
If a user enabled biometric log in from the BlackBerry Dynamics Launcher settings, but dismissed the biometric activation prompt, the biometric log in toggle was still enabled. (GD-62284) |
In some instances, the biometric login screen might have displayed even after it was dismissed by the user. (GD-62269, GD-62275) |
On devices running Android 14, if a user used the BlackBerry Dynamics Launcher to switch between BlackBerry
Dynamics apps, the screen might have appeared blank after navigating to a new app. (GD-62182) |
In some cases, if a user opened the docs section of the BlackBerry Dynamics Launcher on a BlackBerry
Dynamics app, sent the app to the background, and returned it to the foreground, the app might have stopped responding. (GD-62135) |
Known issues
Activating an app on an Android 14 emulator will fail if you provision the app with biometric log in. (GD-61557) |
Play Integrity attestation will fail during app provision on an Android emulator. (GD-61278) |
Users cannot upload files from Google Drive by selecting the file from the native Android file picker. (GD-60021) |
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) |
The Android runtime permission POST_NOTIFICATIONS is no longer required by BlackBerry Dynamics SDK for Android 11.0 and later. 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 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 battery saving mode is enabled and 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) |