Skip to content
Help and manuals  >  Enterprise services  >  BlackBerry Dynamics SDK for Android  >  Release notes and advisories

BlackBerry Dynamics SDK for Android version 4.2

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

Feature

Description

Changes to software requirements

  • The minimum API level for the BlackBerry Dynamics Handheld Library is now 21. Previously it was 19.
  • The minimum API level for the BlackBerry Dynamics Wearable Library is now 21. Previously it was 20.
  • For Android Wear dependencies, the required Google Play Services version is now 11.0.1. Previously, it was 9.1.2.
  • The suggested version of Android Studio is 3 or later.
  • The following values are recommended for sdk/libs/handheld/gd/build.gradle:
    • com.android.tools.build:gradle: 2.3.2 (previously 2.1.0)
    • compileSdkVersion 28 (previously 24)
    • buildToolsVersion "28.0.0" (previously 25.0.3)

Readiness for Android P

This release of the BlackBerry Dynamics SDK for Android adds readiness support for the upcoming release of the Android P operating system. It is a mandatory upgrade that is required to support Android P.
  • Stability and validation: BlackBerry has updated the BlackBerry Dynamics SDK to work as expected with Android P.
  • Hardware security: BlackBerry has validated that current BlackBerry Dynamics hardware security features work as expected with Android P. Support for new hardware security features is pending for future releases of the SDK.
  • Per-app SELinux domains: Android P introduces changes to sharing data between apps using world-accessible Unix permissions. BlackBerry has validated that the SDK operates as expected with these changes.
  • Display cutout support: Android P introduces display cutout support. BlackBerry has updated the SDK to account for this support.
  • Hostname verification changes: Android P introduces changes to hostname verification using a certificate. BlackBerry has updated the SDK to account for this change.
  • Autofill: Android P includes improvements to the autofill framework. BlackBerry has updated the SDK to ensure that this change does not result in data leakage.

API changes

  • The following classes are now optional, not mandatory:
    • GDAppEventListener
    • GDStateListener
  • This release of the SDK has been updated to use SQLite 3.22.

Fixed issues

The following issues are fixed in this release:
  • If a BlackBerry Dynamics app requested authentication from an authentication delegate, but the app was repeatedly uninstalled and reinstalled during the activation request, the app failed to activate with an unspecified error. (FIRST-15575)
  • If your organization used a BlackBerry Dynamics profile (UEM) or security policy (standalone Good Control) to prevent users from reusing old passwords, this setting was not enforced if the user locked the app by entering the wrong password multiple times and then had to specify a new password after providing an app unlock key. (FIRST-15436)
  • In certain circumstances, a user may have been prompted at random intervals to provide an unlock key for the BlackBerry Dynamics container. (FIRST-15221)
  • If FIPS was enabled and a user’s Personal Information Exchange file (.p12, .pfx, .pkcs12) could not be imported because it was not encrypted with FIPS-strength algorithms, the user received a “wrong password” error message. In this release, a more accurate error message is provided. (FIRST-15206)
  • If you enabled Data Leakage Prevention policies in the management console, when a user pasted copied text, the text might have lost some of its previous formatting. (GD-32734)

Known issues

  • On an Android P device, if the Prevent Screen Capture security policy setting is disabled, the user can cut/copy/share data from a BlackBerry Dynamics app to a non-BlackBerry Dynamics app, even when data leakage prevention (DLP) is enabled via Pixel Launcher functionality. To prevent data leakage, it is recommended that you enable the Prevent Screen Capture policy setting. (GD-36449)