Skip Navigation

BlackBerry Dynamics SDK for iOS
version 13.0

What's new in the
BlackBerry Dynamics SDK for iOS
version 13.0

Changes to the SDK and software requirements:
Feature
Description
Integration of the
BlackBerry Dynamics Launcher
with the SDK
In this release, the
BlackBerry Dynamics Launcher
has been implemented into the
BlackBerry Dynamics SDK for iOS
. Previously, the Launcher required the integration of a separate
BlackBerry Dynamics Launcher Library
.
For more information about the integration of the Launcher into the SDK, see Implementing the BlackBerry Dynamics Launcher. The documentation for Launcher integration has now been incorporated into the Dynamics SDK Development Guide.
SDK changes related to the integration of the
BlackBerry Dynamics Launcher
  • The following methods have been deprecated in GTLauncherViewController:
    • setGDPushConnectionStatus
    • startServicesWithOptions
  • The version method has been renamed to launcherVersion
  • The following methods have been added (previously they were in the GTLauncherGoodApplication.h header):
    • setSectionEnabled
    • isSectionEnabled
  • GDiOS has a new method, getManagedLauncherViewController, to return the Launcher instance if it is managed by the
    BlackBerry Dynamics SDK
    .
Recommendation for
Apple
Face ID shortcut
BlackBerry
recommends that you do not enable the
Apple
"Require Face ID" shortcut, because it can interfere with how
BlackBerry Dynamics
apps use Face ID to authenticate a user when launching the app.

Fixed issues

On devices running
iOS
17, the dictation icon was not being removed from
BlackBerry Work
email fields (To, CC, BCC, and Subject) while the
BlackBerry Dynamics
dictation policy was turned on. (GD-62423)
On devices running
iOS
17, if a user attempted to paste an image or GIF into a text field of a
BlackBerry Dynamics
app, the app would force shutdown. (GD-62422)
On devices running
iOS
17, if a user was screen recording, the device might have failed to recognize a change in screen orientation on
BlackBerry Dynamics
apps. (GD-62310)
Autofill was available in the
BlackBerry Dynamics
UI and the placeholder text would still display after autofill. (GD-62208)
Users were unable to use the backspace or delete key on the email address text box after they clicked the back button on the Activation screen. (GD-62191)
On devices running
iOS
17, users were able to insert password into the body of an email by using autofill. (GD-62161)
On devices running
iOS
17, in some cases, if a user opened the docs section of the
BlackBerry Dynamics Launcher
on a
BlackBerry Dynamics
app, sent the app to the background, and returned it to the foreground, the app may have stopped responding. (GD-62135)
On devices running
iOS
17, if a user entered a certificate password and then deleted the characters in the password field, the deleted characters would autofill in the password field when the user attempted to reenter the password. (GD-62133)
On devices running
iOS
17, users were able to insert a contact number into the body of an email while the data leakage prevention policy was turned on. (GD-62050)

Known issues

In
BlackBerry Access
, users are able to take screenshots of videos playing in full screen mode even if the "
iOS
Screenshots Prevention" policy is enabled. (GD-64099)
On an
Apple Watch
, users are able to take screenshots of
BlackBerry Work
even if the "Do not allow screen captures on
iOS
devices"
BlackBerry Dynamics
profile setting is enabled. (GD-62706)
On devices running
iOS
17, if a user attempts to copy text from a PDF in a WKWebView app, the user will not be able to copy the text as the prompt does not appear. (GD-62254)
When using NSURLSession for NTLM authentication, if the password includes a non-ASCII character (for example, "ä"), the authentication attempt will fail. (GD-61708)
If a user provisions a
BlackBerry Dynamics
app using biometric authentication (Touch ID or Face ID) while the "Permit fallback to device passcode if biometric authentication fails" policy is enabled, sends the app to the background, returns the app to the foreground, and selects "Don't Allow" at the Face ID prompt, the user is forced to use the device passcode to unlock the container instead of the container password. The user could not use the container password to unlock the app when it is sent to the background and returned to the foreground again. (GD-59075)
Workaround
: The user must restart the app to use the container password. To re-enable Face ID authentication to the app, the user must go to Device Settings > Face ID and Passcode > Other Apps and enable Face ID for the app.
If a
BlackBerry Dynamics
app uses
Kerberos
authentication and the app tries to access a web page using an IP address, after the user enters their credentials, the web page does not load as expected and the user is prompted to enter their credentials again in a loop. (GD-54481)
Workaround
: When you develop
BlackBerry Dynamics
apps, do not hard code URLs that use IP addresses. If users can manually enter a URL, instruct users to avoid URLs that use an IP address.