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

BlackBerry Dynamics SDK for Android
 version 14.1

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

Changes to the SDK and software requirements:
Feature
Description
Background Authorize
This release adds support for a new
BlackBerry Dynamics
 profile background activity setting that was introduced in
UEM
 version 12.21. This setting allows background process restarts if the OS has terminated the application process. When enabled, a
BlackBerry Dynamics
 app may use secure networking and storage in the background after receiving a push notification. This feature (known as Background Authorize) was previously supported only for select
BlackBerry Dynamics
 apps, required a registration token from
BlackBerry
, and was configured in the app policy. It is now supported for all
BlackBerry Dynamics
 apps and is configured in the
BlackBerry Dynamics
 profile.

Known issues and limitations

If you enable “Do not allow copying data from BlackBerry Dynamics apps into non BlackBerry Dynamics apps” in a
BlackBerry Dynamics
 profile, the “Character limit for cut and copy” allows you to specify how many characters users are permitted to copy from a
BlackBerry Dynamics
 app to non-
BlackBerry Dynamics
 apps. The character limit option was introduced in
UEM
 12.21 and requires
BlackBerry Dynamics
 apps with SDK version 14.0 or later. Any
BlackBerry Dynamics
 profiles that existed before the upgrade to
UEM
 12.21 or later will display the default value of 30 for the character limit option, but the limit is not enforced until you make a change to the profile and save it. (EMM-157418)
If a
BlackBerry Dynamics
 app is configured for biometric authentication, when a device user force stops the app and then changes the system time or time zone, when the user restarts the app, the app does not receive the new time updates and may not provide the expected biometric authentication prompt. (GD-63799)
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 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)