Skip Navigation

BlackBerry Dynamics SDK for Android
version 10.2

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

Changes to the SDK and software requirements:
Feature
Description
Changes to
Android
8 support
Support for
Android
8 has been removed in this release.
Changes to
Android
custom keyboard support
Support to enable or disable
Android
custom keyboards using a
BlackBerry Dynamics
profile setting has been added in this release. This setting is disabled by default and administrators will need to enable it to block the use of Android custom keyboards.
BlackBerry
WebView Library
The following changes have been made to
BlackBerry
WebView in this release:
  • File downloading into the secure container is now supported.
  • The following APIs have been added to the BBWebView library:
    • BBWebView.getDownloadDirectoryPath
    • BBWebView.showDownloadDirectory

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
version 3.4.0.228.

Fixed issues

The following issues are fixed in this release:
A compliance alert message now will display the date in the correct language on the device. (FIRST-17793)
An issue where profiles were still being displayed in UEM after the device credentials were reset, has been resolved. (GD-57966)
After a user credential profile is successfully enrolled, the app now refreshes and updates the profile on the KeyManager
Assigned Profiles
page. (GD-57964)
An issue where apps built with
BlackBerry Dynamics SDK
would get stuck at the splash screen after setting the password following the app provision process, has been resolved. (GD-57952)
An issue where screenshots and videos could be captured while the
Do not allow screen capture and insecure video output on Android and Windows 10 devices
policy was enabled in the users
BlackBerry Dynamics
profile, has been resolved. Video and screenshot capturing can only be done while the policy is disabled. (GD-57757)
An issue where data could be copied from BlackBerry Dynamics apps to non-BlackBerry Dynamics apps, despite the
BlackBerry UEM
user policy preventing it, has been resolved.(GD-57756)
An issue has been resolved where if the user force closes an app during the easy activation process, they will receive a notification stating
Failed to Connect to Push Channel
. The app will now begin the activation process from the beginning when the app is started again. (GD-57221)

Known Limitations

If a user switches from a third-party keyboard to the system keyboard, in some deployment configurations the application may take a minute to detect the change and remove the
Custom Keyboards Restricted
notification. (GD-57693)
Workaround:
When the user restarts the app they can use the system keyboard immediately.

Known issues

If you use direct references to the
BlackBerry Dynamics
SDK .aar files in your build.gradle repositories (for example, compile(name:'android_handheld_platform-8.1.0.57', ext:'aar')) instead of using Maven linkage (for example, api "com.blackberry.blackberrydynamics:android_handheld_platform:8.1.0.57"), errors may occur in the AndroidManifest file in the
Gradle
caches directory. To resolve, use Maven linkage or specify android_handheld_resources and android_handheld_platform in the build.gradle file.
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
.
If a user is prompted to activate a
BlackBerry Dynamics
app using their password for another
BlackBerry Dynamics
app that they have previously activated (also known as Easy Activation), then cancels out of the prompt, the lock screen for the previously activated app displays instead of the screen to enter their activation credentials. (GD-56598)
If "Allow
Android
biometric authentication" is enabled in the
BlackBerry Dynamics
profile, when the user activates a
BlackBerry Dynamics
app on an
Android
12 emulator, fingerprint authentication fails for the app with the error message "Internal error: Retry or restart". (GD-56289)
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, this functionality does not work as expected (the app does not prompt the user for their password when it returns to the foreground). (GD-56162)
If a user upgrades a
BlackBerry Dynamics
app that uses SDK version 9.x or earlier to a new version that uses SDK 10.1 or later, the app will not retain any cookies. (GD-55766)
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 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.