Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Dynamics Bindings for Xamarin.Android 11.0
  3. BlackBerry Dynamics SDK for Xamarin Release Notes
  4. BlackBerry Dynamics Bindings for Xamarin.iOS 11.0

BlackBerry Dynamics Bindings for Xamarin.iOS
 11.0

What's new in
BlackBerry Dynamics Bindings for Xamarin.iOS
 11.0

This release includes updates from the
BlackBerry Dynamics SDK for iOS
 version 10.2 and 11.0. For more information, see the BlackBerry Dynamics SDK for iOS Release Notes.
Feature
Description
Changes to SDK and software requirements
  • Xamarin.iOS
     16.0.0.72 or later is required.
  • Microsoft Visual Studio
     for
    macOS
     17.3.6 or later is required.
Changes to
iOS
 13 support
Support for
iOS
 13 has been removed in this release.
Changes to support for WebRTC
WebRTC can now be turned on or off in the app configuration settings. Support for WebRTC is blocked by default.
WebRTC is an optional integration for
BlackBerry Dynamics SDK for iOS
, which does not support the use of WebRTC. Since the SDK does not support WebRTC traffic, users are accepting a possible security risk when approving the use of WebRTC. For more information, see Enabling microphone and camera support with WebRTC in the iOS Development guide.
iOS
 16 readiness
iOS
 16 is supported in this release of
BlackBerry Dynamics Bindings for Xamarin.iOS
. During the easy activation process, users will receive an Allow Paste prompt when switching to authentication delegate if the app is using
BlackBerry Dynamics Bindings for Xamarin.iOS
 for iOS version 10.1. As a result, you must update
BlackBerry Dynamics Bindings for Xamarin.iOS
 to version 11.0 to avoid this usability issue.
Support for Xcode 14
Xcode 14 is supported in this release of
BlackBerry Dynamics Bindings for Xamarin.iOS
 for the following software configuration:
  • Microsoft Visual Studio
     for
    macOS
     2022 version 17.3.6 or later with
    Xamarin.iOS
     16.0.0.72 or later
WKWebView enhancements
The following WkWebView enhancements are new in this release of
BlackBerry Dynamics SDK for iOS
:
  • HTML5 persistent local storage is now supported.
Third-party IDP activation enhancements
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.
Changes to Easy Activation on
iOS
 16
If a user is shown the password authentication screen during the Easy Activation process, the UI will now display the
BlackBerry
 icon instead of the icon for the app that is requesting activation.
Authentication enhancements
If a user's biometric authentication fails, they will be permitted to authenticate using their device passcode if the
UEM
 policy
Permit fallback to device passcode if biometric authentication fails
 is enabled by their
UEM
 administrator.
Unsupported NSURLSession properties
The following NSURLSession properties are new in
iOS
16 and are not yet supported by
BlackBerry Dynamics SDK for iOS
:
  • Class: NSMutableURLRequest
    • property: requiresDNSSECValidation
  • Class: NSURLSessionConfiguration
    • property: requiresDNSSECValidation
Apple
 Live Text limitations
The
Apple
 Live Text APIs, introduced in
iOS
 16, allow apps to interact with text inside of images and perform an action on that text such as copy and paste. These APIs are not secured by
BlackBerry Dynamics SDK for iOS
 and can not be limited by a DLP policy. As a result,
BlackBerry
 recommends that you do not use the following APIs in your app:
  • ImageAnalyzer
  • ImageAnalysis
  • ImageAnalysisInteraction
  • ImageAnalysisInteractionDelegate

BlackBerry Dynamics Launcher Library

This release uses
BlackBerry Dynamics Launcher Library
 version 3.5.0.328.

Known issues and limitations

  • When building a
    BlackBerry Dynamics
     Xamarin app in
    Visual Studio
    , the following warning might display: "App
    <name>
     cannot be opened because the developer cannot be verified." Native linking errors occur in the build log. This occurs when Catalina 10.15 considers the unpackaged SDK artifacts as untrusted.
    Workaround
    :
    1. Unzip the SDK package.
    2. Run the terminal and change the directory to the location of the unzipped package.
    3. Run the following command:
      xattr -dr com.apple.quarantine ./
  • When building a
    BlackBerry Dynamics
     Xamarin app for an
    iOS
     simulator in
    Visual Studio
    , MT5209 native linking errors might occur.
    Workaround
    : In the
    iOS
     build options, turn off "Enable device-specific builds".