BlackBerry Dynamics SDK for iOS version 11.0
BlackBerry Dynamics SDK for iOS
version 11.0What's new in the BlackBerry Dynamics SDK for iOS version 11.0
BlackBerry Dynamics SDK for iOS
version 11.0Changes to the SDK and software requirements:
Feature | Description |
---|---|
iOS 16 readiness | iOS 16 is supported in this release of BlackBerry Dynamics SDK for 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 SDK for iOS version 10.2 or 10.1. As a result, you must update BlackBerry Dynamics SDK for iOS to version 11.0 to avoid this usability issue. |
Upcoming changes to BlackBerry Dynamics SDK for iOS static library support | Support for the BlackBerry Dynamics SDK for iOS static library will be deprecated in the 11.1 release and will no longer be available in a future release. At that time, BlackBerry Dynamics SDK for iOS will support the dynamic framework only. For more information, see Using the BlackBerry Dynamics SDK dynamic framework. |
WKWebView enhancements | The following WkWebView enhancements are new in this release of BlackBerry Dynamics SDK for iOS :
|
Support for Apple Silicon M1 devices | The following are now supported in this release of BlackBerry Dynamics SDK for iOS :
|
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 :
|
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:
|
BlackBerry Dynamics Launcher Library
BlackBerry Dynamics Launcher Library
This release uses
BlackBerry Dynamics Launcher Library
version 3.5.0.328Fixed issues
The following issues are fixed in this release:
An issue where BlackBerry Tasks or BlackBerry Notes would close when navigating to a different BlackBerry app from the BlackBerry Dynamics Launcher , has been resolved. (GD-59086) |
An issue where the spacing between UI elements would change when the device would change from portrait to landscape mode, has been resolved. (GD-59083) |
An issue where multiple credential prompts would display when setting up a Kerberos authentication method type test, has been resolved. (GD-59074) |
An issue where the screen would continuously flash during the setup process on DEP devices has been resolved. (GD-58559) |
An issue where a BlackBerry
Dynamics app that used ASWebAuthenticationSession with a Kerberos , NTLM, Digest, or Basic URL, would receive a 401 status code and would not prompt the user to enter their sign in credentials, has been resolved. (GD-56706) |
Known issues or limitations
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 will be forced to use the device passcode to unlock the container instead of the container password. The user will not be able to use the container password to unlock the app when it is sent to the background and returned to the foreground again.Workaround : The user must restart the app to be able 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. |
On iOS 16, dictation is still operational even if the Do not allow iOS dictation BlackBerry
Dynamics profile setting is enabled. (GD-59536) |
On iOS 16, if a user views a .pdf in web view and long presses on some text in the file, a second pasteboard will appear with the buttons Look up , Translate , and Share . The Translate and share buttons are not operational. The Look up button will display a preview, but it is not active and the user will not be able to navigate through it. (GD-58940) |
If a BlackBerry
Dynamics app uses the BlackBerry
Dynamics static library, you will not be able to build that app on an Apple M1 simulator. |
If a user upgrades a BlackBerry
Dynamics app that uses SDK version 9.x or earlier to a new version that uses SDK 10.1 or later, the app will not retain any cookies. (GD-55766) |
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. |
When an Apple M1 device user tries to remove a BlackBerry
Dynamics app binary by moving it to the trash, the secure container is not removed from the device. (GD-53650)Workaround: The user must delete the folder under ~/Library/Containers/BB_App_Name. |