Skip Navigation

BlackBerry Dynamics SDK for Android
version 7.1

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

New SDK features and changes
Feature
Description
Zero sign-on for SaaS services through
BlackBerry Enterprise Identity
Your custom
BlackBerry Dynamics
apps can leverage zero sign-on (ZSO) for SaaS through
BlackBerry Enterprise Identity
. For more information, see the BlackBerry Enterprise Identity Administration content.
Deprecating READ_PHONE_STATE permission in an upcoming release
Support for the READ_PHONE_STATE permission will be removed from the
BlackBerry Dynamics SDK for Android
in the next major release of the SDK. This permission is no longer required.
If you currently leverage this permission, you will need to add support for your own phone permission.
New administrative and security features
Feature
Description
Compliance prompt interval
SDK version 7.1 and
UEM
version 12.12 or later add support for compliance prompts for
BlackBerry Dynamics
app users. Using a compliance profile, an administrator can specify the type, count, and interval for prompts before
UEM
executes a compliance action (for example, blocking
BlackBerry Dynamics
apps or deleting
BlackBerry Dynamics
app data).
Migrating
BlackBerry Dynamics
users between
UEM
domains
SDK version 7.1 and
UEM
version 12.12 MR1 support migrating
BlackBerry Dynamics
users between
UEM
domains. For more information, see the UEM version 12.12 Configuration Guide.
Deprecation of a setting in
BlackBerry Dynamics
profiles
The "Require password when
BlackBerry Dynamics
apps return to the foreground" setting in
BlackBerry Dynamics
profiles will be removed in an upcoming release.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
version 3.0.1.175.

Supported TLS protocols and cipher suites

The
BlackBerry Dynamics SDK
supports the following TLS protocols and cipher suites. Note that SSL version 3 or older is no longer supported. A
BlackBerry Dynamics
app that is upgraded to SDK version 7.0 or later might stop connecting to SSL application servers if the app uses weak ciphers.
Supported TLS version 1.2 cipher suites:
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
  • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
  • TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 (0x00a3)
  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
  • TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
  • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
  • TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 (0x00a2)
  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
  • TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b)
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067)
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  • TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
  • TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  • TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
  • TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  • TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)
Supported TLS version 1.1 cipher suites:
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  • TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  • TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  • TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)
Supported TLS version 1.0 cipher suites:
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  • TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  • TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  • TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)

Fixed issues

The following issue are fixed in this release:
  • Traffic from
    BlackBerry Dynamics
    apps was not balanced across multiple
    BlackBerry Proxy
    instances as expected. (FIRST-17190/GD-49121)
  • If an administrator restricted versions of a
    BlackBerry Dynamics
    app using the
    UEM
    management console, the way the restricted version number was processed may have unintentionally blocked more versions of the app than intended. (FIRST-17124)
  • On
    OnePlus
    and Redmi devices, in certain circumstances,
    BlackBerry Dynamics
    apps could get stuck in an authentication loop. (FIRST-17108)

Known issues and limitations

  • Upgrading a device to
    Android
    11 (target SDK 30) might result in a false positive rooted detection event. To resolve this issue, upgrade to SDK version 8.1.
  • If a user connects a device to a
    Windows
    or
    Mac
    computer with a USB cable and launches
    Samsung DeX
    , then opens a
    BlackBerry Dynamics
    app on the device, the
    BlackBerry Dynamics
    sign-in screen displays as black on the computer. This issue is limited to USB connections and does not occur when using the
    Samsung DeX Station
    . (GD-46800)
    Workaround
    : From the black screen, if the user enters their password and presses Enter, the app will log in as expected.
  • If advanced battery optimization options are enabled on a
    OnePlus
    device, Easy Activation, authentication delegation, and other features that require communication between
    BlackBerry Dynamics
    apps do not work as expected. (GD-43162)
    Workaround
    : Turn off battery optimization.