BlackBerry Dynamics SDK for Android version 12.0.0.57
BlackBerry Dynamics SDK for Android
version 12.0.0.57What's new in the BlackBerry Dynamics SDK for Android version 12.0.0.57
BlackBerry Dynamics SDK for Android
version 12.0.0.57Changes to the SDK and software requirements:
Feature | Description |
|---|---|
Android 14 readiness | Android 14 is now supported in this release.BlackBerry recommends upgrading to BlackBerry Dynamics SDK for Android 12.0. If you do not upgrade from version 11.2, you may experience performance issues and battery drain on Android 14, as Android 14 will now queue all events and deliver them when apps are in the foreground. For more information, see Behavior changes: all apps in the Android documentation. |
Security enhancements | The BlackBerry Dynamics SDK for Android now includes security enhancements to improve rooted detection, hooking detection, and emulator detection. |
Enhancements to user passwords | The BlackBerry Dynamics SDK for Android has been updated to improve the flow of changing a user's password. If a user attempts to change their password from a non-authentication delegated app, the device will open an authentication delegated app and will prompt the user to change their password from the authentication delegated app. For more information, see Authentication delegation in the BlackBerry Dynamics SDK for Android development guide. |
UX enhancements | The BlackBerry Dynamics SDK for Android has been updated with enhanced UX to improve iconography, consistency, and clarity on SDK screens. The following updates are new in this release:
|
CURL upgrade | CURL has been updated to version 8.0.0 in this release. |
Heimdal upgrade | Heimdal has been upgraded to version 7.80.0 in this release. |
Changes to BBWebView | The deprecated API BBWebChromeClient.onReachedMaxAppCacheSize has been removed from BBWebView in this release. |
BlackBerry Persona compatibility | The BlackBerry Dynamics SDK for Android will be ending support for BlackBerry Persona in the 12.1 release. You must remove any instances of BlackBerry Persona APIs after the 12.1 release. |
BlackBerry Dynamics Launcher Library
BlackBerry Dynamics Launcher Library
This release uses
BlackBerry Dynamics Launcher Library
version 12.0.0.253Fixed issues
There are no fixed issues in this release. |
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
On devices running Android 14, if a user turns on airplane mode during the retrieving policies stage of the app provision, the app will stop responding. (GD-62564) |
If a BlackBerry
Dynamics app is sent to the background and returned to the foreground, various UI issues may appear on the password screen. (GD-62380) (GD-62273) |
In some instances, the cancel button will not display on the certificate enrollment screen. (GD-62302) |
If a user enables biometric log in from the BlackBerry Dynamics Launcher settings but dismisses the biometric activation prompt, the biometric log in toggle will still be enabled. (GD-62284) |
In some instances, the biometric login screen may display even after it was dismissed by the user. (GD-62275) (GD-62269) |
On devices running Android 14, if a user uses the BlackBerry Dynamics Launcher to switch between BlackBerry
Dynamics apps, the screen may appear blank after navigating to a new app. (GD-62182) |
In some cases, if a user opens the docs section of the BlackBerry Dynamics Launcher on a BlackBerry
Dynamics app, sends the app to the background, and returns it to the foreground, the app may stop responding. (GD-62135) |
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) |
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) |
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) |