BlackBerry Dynamics SDK for iOS version 12.1.1.43
    BlackBerry Dynamics SDK for iOS
 version 12.1.1.43What's new in the BlackBerry Dynamics SDK for iOS version 12.1.1.43
      BlackBerry Dynamics SDK for iOS
 version 12.1.1.43Changes to the SDK and software requirements:
| Feature | Description | 
|---|---|
| SSO for web authentication | You can now use Single Sign-On (SSO) with ASWebAuthenticationSession applications.  | 
| Screenshot prevention | You can prevent users from taking screenshots across all the  BlackBerry
        Dynamicsapps using the new "Do not allow screenshots on iOSdevices" BlackBerry
        Dynamicsprofile setting. If an app policy for screenshot prevention is defined, it will take priority and the profile setting will be ignored. If a device user tries to take a screenshot in a  BlackBerry
        Dynamicsapp after this option is enabled, a blank image with the following message is saved instead: "Your organization prevents screenshots being taken within this app." This option is supported for  BlackBerry
        Dynamicsapps that use BlackBerry Dynamics SDK12.1 and later, and replaces the iOSscreen capture detection rule in compliance profiles. BlackBerryrecommends using the new profile setting and disabling the compliance rule. The compliance rule will be deprecated in a future UEMrelease. For more information, see BlackBerry Dynamics profile settings in the  UEMcontent. | 
| Support for  AppleWatch | This release adds support for  AppleWatch. For more information, see the DynamicsWatch class in the  BlackBerry Dynamics SDK for iOSAPI Reference. | 
| Support for  CylancePROTECT Mobileinsecure Wi-Fiaccess point detection for iOS | UEM12.20 adds support for a new CylancePROTECT Mobilefeature, insecure Wi-Fiaccess point detection for iOS(see Protecting devices from network threats in the CylancePROTECT Mobilecontent). You can leverage this feature in your BlackBerry
        Dynamicsapps. If you want to use the insecure  Wi-Fidetection feature, you must add the Access Wi-Fi Information Entitlement to the app configuration (plist) of your BlackBerry
        Dynamicsapp, and the app must prompt the user to grant location permissions that are required for the insecure Wi-Fifeature to work. The BlackBerry Dynamics SDKcannot automatically prompt the user or grant location permissions for the device. The feature will not work if the user does not grant location permissions ( UEMwill report a compliance issue). | 
| BlackBerry Personacompatibility | The  BlackBerry Dynamics SDK for iOSis no longer compatible with BlackBerry Persona. APIs related to BlackBerry Persona, such as BISThreatStatusAPI, have been removed. | 
BlackBerry Dynamics Launcher Library
      BlackBerry Dynamics Launcher Library
This release uses 
BlackBerry Dynamics Launcher Library
 version 12.1.822.23.Fixed issues
      
  | On devices running  iOS17, the dictation icon was not being removed from BlackBerry Workemail fields (To, CC, BCC, and Subject) while the BlackBerry
        Dynamicsdictation policy was turned on. (GD-62423) | 
| On devices running  iOS17, if a user attempted to paste an image or GIF into a text field of a BlackBerry
        Dynamicsapp, the app would force shutdown. (GD-62422) | 
| On devices running  iOS17, if a user was screen recording, the device might have failed to recognize a change in screen orientation on BlackBerry
        Dynamicsapps. (GD-62310) | 
| Autofill was available in the  BlackBerry
        DynamicsUI 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  iOS17, users were able to insert password into the body of an email by using autofill. (GD-62161) | 
| On devices running  iOS17, in some cases, if a user opened the docs section of the BlackBerry Dynamics Launcheron a BlackBerry
        Dynamicsapp, sent the app to the background, and returned it to the foreground, the app may have stopped responding. (GD-62135) | 
| On devices running  iOS17, 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  iOS17, 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
      
  | On  BlackBerry Access, users are able to take screenshots of videos playing in full screen mode even if the " iOSScreenshots Prevention" policy is enabled. (GD-64099) | 
| On an  Apple Watch, users are able to take screenshots of BlackBerry Workeven if the "Do not allow screen captures on iOSdevices" BlackBerry
        Dynamicsprofile setting is enabled. (GD-62706) | 
| On devices running  iOS17, 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
        Dynamicsapp 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
        Dynamicsapp uses Kerberosauthentication 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
        Dynamicsapps, 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. |