BlackBerry Dynamics SDK for Android version 13.0.2.152
BlackBerry Dynamics SDK for Android
version 13.0.2.152What's new in the BlackBerry Dynamics SDK for Android version 13.0.2.152
BlackBerry Dynamics SDK for Android
version 13.0.2.152Changes to the SDK and software requirements:
Feature | Description |
|---|---|
Integration of the BlackBerry Dynamics Launcher with the SDK | In this release, the BlackBerry Dynamics Launcher has been implemented into the BlackBerry Dynamics SDK for Android . Previously, the Launcher required the integration of a separate BlackBerry Dynamics Launcher Library .For more information about the integration of the Launcher into the SDK, see Implementing the BlackBerry Dynamics Launcher. The documentation for Launcher integration has now been incorporated into the Dynamics SDK Development Guide. |
Support for Android edge-to-edge | By default, the user interface for BlackBerry
Dynamics apps on Android OS 15 or later supports edge-to-edge display mode. |
Notes and requirements for new Android features |
|
Notification when screen recording is not permitted | If an administrator has enabled "Do not allow screen capture and insecure video output" in the assigned BlackBerry
Dynamics profile, users will now receive the following notification if they try to screen record in a BlackBerry
Dynamics app: "Screen recording is not permitted by your organization's policy". |
Fixed issues
Activating an app on the Android emulator failed if you enabled biometric log in. (GD-61557) |
If a user opened a BlackBerry
Dynamics app on an insecure Wi-Fi network while the "Unsafe Wi-Fi detected" compliance action was enabled, they received a dialog stating that the application was blocked for the network. If the user opened the network settings on Android 13 or later, the network settings panel was blank until the user tapped the Settings button from the panel. (GD-59357) |
If you configured the BlackBerry
Dynamics profile to require users to enter their password when a BlackBerry
Dynamics app returned to the foreground, on Android 13 or later devices, the app did not prompt the user for their password when it returned to the foreground. (GD-56162) |
Known issues and limitations
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 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) |