Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Dynamics Bindings for Microsoft.iOS 12.1
  3. BlackBerry Dynamics SDK for Microsoft .NET Release Notes
  4. BlackBerry Dynamics Bindings for Microsoft.Android 12.1

BlackBerry Dynamics Bindings for Microsoft.Android
 12.1

What's new in
BlackBerry Dynamics Bindings for Microsoft.Android
 version 12.1

This release includes updates from the
BlackBerry Dynamics SDK for Android
 version 12.1. For more information, see the BlackBerry Dynamics SDK for Android Release Notes.
Feature
Description
Changes to SDK and software requirements
  • Microsoft.Android
     34.0.95 or later.
  • Microsoft Visual Studio
     for
    macOS
     17.6.12 or later.
.NET upgrade
.NET has been upgraded to version 8.0. For more information, see the
Microsoft
 resource What's new in .NET MAUI for .NET 8 and the
GitHub
 resource Upgrading .NET MAUI from .NET 7 to .NET 8.
To use .NET 8 in
Visual Studio
 Mac, you must select the preview feature "Use the .NET8 SDK if installed".
.NET 8 target framework
.NET 8 supports API 34 or later.
New
BlackBerry Dynamics Launcher
 API
This release introduces a simplified
BlackBerry Dynamics Launcher
 API. For more information, see Implement the BlackBerry Dynamics Launcher and see the changes in ApacheHttp in this release.
Changes to
Android
 compatibility
The
BlackBerry Dynamics SDK for Android
 is no longer compatible with
Android
 10 (API 29).
Changes to
Java
 compatibility
Java
 17 or later is now required for development with the
BlackBerry Dynamics SDK for Android
.
Deprecation of
BlackBerry Persona
 compatibility
The
BlackBerry Dynamics SDK for Android
 is no longer compatible with
BlackBerry Persona
. APIs related to
BlackBerry Persona
, such as BISThreatStatusAPI, have been removed.

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
 version 12.1.590.4.

Known issues and limitations

Due to a
Microsoft Visual Studio
 for
Mac
 packaging issue, a runtime error might occur after switching to library level ProGuard dependencies.
Workaround
: Clean bin/obj project folders, clean project, restore dependencies, rebuild, and then deploy the application. In addition, when switching between
Microsoft Visual Studio
 for
Mac
 and your terminal (CLI dotnet build), the bin/obj folders must be cleaned or the "--no-incremental" parameter must be used. A build time warning has been added to the sample applications to pay special attention to this issue.