Get the PDF

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.

If you are upgrading a version of the SDK earlier than 3.2.x, in addons.xml you will see 2 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.

If your organization is migrating from standalone
Good Control
5.0 to
BlackBerry UEM
12.8 MR1 or later
: Prior to the migration, you must rebuild your custom

BlackBerry Dynamics

apps using version 4.0.0 or later of the SDK and update the apps on users’ devices. Any

BlackBerry Dynamics

apps that were built with a version earlier than 4.0.0 will be wiped during the migration process (the

UEM

administrator will receive a warning about this prior to starting the migration process). After migration, the apps will have to be removed from devices and reinstalled to work as expected.

Please check with your ISV app providers to verify that they meet this requirement as well.

For more information about the migration process, prerequisites, and considerations, see the BlackBerry UEM Configuration Guide.