BlackBerry Dynamics Bindings for Xamarin.Android 11.0

This release adds support for devices using

Android

13. Due to new intent filtering on

Android

13, which impacts easy activation, authentication delegation, and intercontainer communications (ICC), you must update

BlackBerry Dynamics Bindings for Xamarin.Android

to version 11.0.

As a result of the new intent filtering, apps that target Android 13 (API level 33) will only be supported in the upcoming

BlackBerry Dynamics Bindings for Xamarin.Android

release.

Support for Android 13 requires an update to the

Java

Development Kit. For more information see Java compatibility in the

BlackBerry Dynamics Bindings for Xamarin.Android

software requirements.

Support for

Android

8 has been removed in this release.

The clearPrimaryClip() function has been added to the ClipboardManager class in this release of BlackBerry Dynamics SDK for Android. For more information, see ClipboardManager in the BlackBerry Dynamics API reference.

Users can now activate a

BlackBerry Dynamics

app through a third-party IDP, such as

Active Directory

or

Okta

. Users can also sign in using their organizational credentials if they need to reset their app password or if their app has been locked. If this feature is enabled by an administrator, users will not need to request an unlock code through UEM self-service or from their administrator.

Support to enable or disable

Android

custom keyboards using a

BlackBerry Dynamics

profile setting has been added in this release. This setting is disabled by default and administrators will need to enable it to block the use of Android custom keyboards.