BlackBerry Dynamics SDK for iOS version 12.0.0.57
BlackBerry Dynamics SDK for iOS
version 12.0.0.57What's new in the BlackBerry Dynamics SDK for iOS version 12.0.0.57
BlackBerry Dynamics SDK for iOS
version 12.0.0.57Changes to the SDK and software requirements:
Feature | Description |
|---|---|
iOS 17 readiness | This release adds support for iOS 17. |
Enhancements to BlackBerry Dynamics device security | The BlackBerry Dynamics SDK for iOS now includes security enhancements to improve jailbreak detection, hooking detection, and emulator detection. |
Enhancements to user passwords | The BlackBerry Dynamics SDK for iOS has been updated to improve the flow of changing a user's password. If a user attempts to change their password from a non-authentication delegated app, the device will open an authentication delegated app and will prompt the user to change their password from the authentication delegated app. For more information, see Authentication delegation in the BlackBerry Dynamics SDK for iOS development guide. |
CURL upgrade | CURL has been updated to version 8.0.0 in this release. |
Heimdal upgrade | Heimdal has been upgraded to version 7.8.0 in this release. |
BlackBerry Persona API support | The BlackBerry Dynamics SDK for iOS will be ending support for BlackBerry Persona in the 12.1 release. You must remove any instances of BlackBerry Persona APIs after the 12.1 release. |
BlackBerry Dynamics Launcher Library
BlackBerry Dynamics Launcher Library
This release uses
BlackBerry Dynamics Launcher Library
version 12.0.0.378.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) |
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 or limitations
The provision screen of a BlackBerry
Dynamics app does not appear on app startup after the app data was remotely deleted from UEM . (GD-62796) |
On Apple Watch , users are able to take screenshots of a BlackBerry
Dynamics app, while "Do not allow screen captures on iOS devices" is enabled in the BlackBerry
Dynamics profile settings. (GD-62706) |
On devices running iOS 17, if a user is screen recording, the device may fail to recognize a change in screen orientation on BlackBerry
Dynamics apps. (GD-62310) |
On devices running iOS 17, if a user long taps on a link from a WKWebView app and selects "Add to reading list", the app will stop responding. (GD-62257) |
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. |