Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Dynamics SDK for Android 7.1
  3. BlackBerry Dynamics SDK for Android Release Notes
  4. Installing or upgrading the software

Installing or upgrading the software

For complete installation instructions, upgrade guidance, and software requirements, see the BlackBerry Dynamics SDK for Android Development Guide. The Development Guide also provides instructions for implementing the SDK libraries as .aar files that can be published to an internal repository.
If you installed the SDK using 
Android Studio
 SDK manager and you made changes to the sample apps, the update might override the sample apps, discarding your changes.
  • The 
    BlackBerry Dynamics SDK for Android
     5.0 and later includes a compliance enhancement to protect against malicious attempts to add a debugger to deployed 
    BlackBerry Dynamics
     apps. Your options for configuring this feature depend on the version of 
    BlackBerry UEM
     and the 
    BlackBerry Dynamics SDK
    . For more information, see Configure compliance settings so you can debug your app in the 
    BlackBerry Dynamics SDK
     Development Guide.
  • If you are upgrading a version of the SDK earlier than 3.2.x, in addons.xml you will see two entries named Dynamics_SDK, one from 
    BlackBerry
     and one from 
    Good
    . The 
    Good
     entry should be removed.
  • Note that the install path of the SDK has changed from ANDROID_HOME/extras/
    good
    /dynamics_sdk/sdk to ANDROID_HOME/extras/
    blackberry
    /dynamics_sdk/sdk. Please update your app project files to load the SDK from the new location.
    If you installed the SDK using the 
    Android
     SDK Manager and you used import module to include the 
    BlackBerry Dynamics Runtime
     in app projects, you must now import from the new location. If you used a reference to do this (for example, a project Gradle definition or a custom build script), you must update references as required to use the new location.
    Currently, the 
    BlackBerry Dynamics SDK for Cordova
     includes a Configure plug-in that does not work with the new install path. This will be fixed in an upcoming release. As a temporary workaround, please set the Configure plug-in to use Explicit mode, which allows you to specify the correct path.
  • If you plan to install the SDK using the 
    Android
     SDK Manager and you are upgrading to 
    BlackBerry Dynamics SDK
     version 4.0 or later, note that there is a change to the extracted folder structure in the extras/blackberry/dynamics_sdk folder. At this level there is now an m2repository/ folder for .aar distribution, and an sdk/ folder that contains the original .jar distribution and resources. You must edit your settings.gradle files as necessary to account for the extra sdk/ folder at this level.