Skip Navigation

BlackBerry Dynamics SDK for Android
version 13.2.0.34

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

Changes to the SDK and software requirements:
Feature
Description
Changes to software requirements
  • Android
    11 is no longer supported.
    Android
    12 or later is required.
  • The minimum Gradle version is now 8.9 (previously 8.0)
  • The required
    Android
    Gradle Plug-in (com.android.tools.build:gradle) is 8.6.1 (previously 8.1.1)
Support for 16 KB page sizes
Android
has announced that, starting November 1, 2025, all new and updated apps targeting
Android
15 and later must support 16 KB page sizes. For more information, see Android Developers: Support 16 KB page sizes and Android Developers Bog: Get your apps ready for 16 KB page size devices.
This release of the
BlackBerry Dynamics SDK
is compatible with the 16 KB page size requirement. It is recommended that you run a mock submission of custom
BlackBerry Dynamics
apps to
Google Play
to identify any additional dependencies that you need to resolve to meet the 16 KB page size requirement.

Fixed issues

Inter-Container Communication (ICC) between
BlackBerry Dynamics
apps uses TLS 1.2 when both apps are using SDK version 13.2 or later. If either
BlackBerry Dynamics
app uses an earlier SDK version, TLS 1.0 is used. (GD-67575)

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
12 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)