Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Dynamics SDK for iOS 4.2
  3. BlackBerry Dynamics SDK for iOS Release Notes
  4. BlackBerry Dynamics SDK for iOS version 4.2

BlackBerry Dynamics SDK for iOS
 version 4.2

What's new in 
BlackBerry Dynamics SDK for iOS
 version 4.2

Feature
Description
Readiness for 
iOS
 12
This release of the 
BlackBerry Dynamics SDK for iOS
 adds readiness support for the upcoming release of the 
iOS
 12 operating system. It is a 
mandatory upgrade
 that is required to support 
iOS
 12.
  • Stability and validation
    :
    BlackBerry
     has updated the 
    BlackBerry Dynamics SDK
     to work as expected with 
    iOS
     12.
  • Password Autofill
    : Previously, if a user enabled Password Autofill for a 
    BlackBerry Dynamics
     app and used the autofill feature when unlocking the app, the app stopped responding. Use of the autofill feature for unlocking 
    BlackBerry Dynamics
     apps has now been disabled.
  • Replay Kit
    : The 
    BlackBerry Dynamics SDK for iOS
     does not currently support the ReplayKit framework.
  • Xcode
     10 support
    : Due to the new 
    Xcode
     build system, apps cannot be built by default with 
    Xcode
     10. The workaround is to use the legacy build system.
Support for WKWebView
The 
BlackBerry Dynamics SDK for iOS
 version 4.2 and later supports secure WKWebView for displaying interactive web content. The SDK supports WKWebView for devices running 
iOS
 11.0 or later.
For more information about supported and unsupported features, see "Support for WKWebView" in the Development Guide.
Add the WKWebview.framework
The 
BlackBerry Dynamics
 runtime static library requires the WKWebview.framework to be included in the Link Binary With Libraries build phase.
API changes
  • The GDiOSDelegate class is now optional, not mandatory.
  • This release includes changes to the implementation of data leakage prevention (DLP). If an outbound DLP policy from 
    BlackBerry UEM
     or standalone 
    Good Control
     applies to a user, when the user taps "Open Link" or "Add to Reading List" on the long press action sheet, the action does not take place and a DLP error message is displayed.
  • The 
    iOS
     UIAlertView class is deprecated in 
    iOS
     8. For more information, see Class: UIAlertView.
  • The 
    iOS
     UIActionSheet class is deprecated in 
    iOS
     8. For more information, see Class: UIActionSheet.
  • This release of the SDK has been updated to use SQLite 3.22.

Deprecated items

  • GDFileSystem was deprecated in the 
    BlackBerry Dynamics SDK for iOS
     version 4.0.

Compatibility with the 
BlackBerry Dynamics Bindings for Xamarin.iOS
 4.0

The 
BlackBerry Dynamics Bindings for Xamarin.iOS
 version 4.0.x is not compatible with the 
BlackBerry Dynamics SDK for iOS
 version 4.2.x.

Fixed issues

The following issues are fixed in this release:
  • In some cases, after upgrading a 
    BlackBerry Dynamics
     app, the app was remote locked due to a threading issue on startup. This issue is resolved in hotfix 4.2.0.145. (GD-37088)
  • If you enabled Data Leakage Prevention policies in the management console, when a user pasted copied text, the text might have lost some of its previous formatting. (GD-32734)
  • Easy activation did not complete successfully if the app was open in split-view and a password change was required by the banned passwords rule in the 
    BlackBerry Dynamics
     profile (
    UEM
    ) or by a security policy (standalone 
    Good Control
    ). (GD-31211)
  • If a 
    BlackBerry Dynamics
     app used the 
    iOS
     UIPasteBoard API, the app might have stopped responding. (FIRST-15609)
  • If a 
    BlackBerry Dynamics
     app requested authentication from an authentication delegate, but the app was repeatedly uninstalled and reinstalled during the activation request, the app failed to activate with an unspecified error. (FIRST-15603)
  • If FIPS was enabled and a user’s Personal Information Exchange file (.p12, .pfx, .pkcs12) could not be imported because it was not encrypted with FIPS-strength algorithms, the user received a “wrong password” error message. In this release, a more accurate error message is provided. (FIRST-15571)
  • Logs could contain an excessive number of UTIL:MBD entries that are related to progress notifications. Improvements have been made to prevent an excessive number of these entries. (FIRST-15444)
  • If a user's device was set to certain languages such as French, Chinese, or Japanese, and a 
    BlackBerry Dynamics
     app opened a Core Data persistent store using GDEncryptedBinaryStoreType (see the GDPersistentStoreCoordinator class), the call failed. (FIRST-15337)
  • If you upgraded the 
    BlackBerry Dynamics SDK for iOS
     from 3.3.x to a later version, and FIPS was enabled, the app might not have provided an accurate error message when a user tried to connect to a website with an invalid SSL certificate. As a result, the user could not access the prompt to "Proceed This Time" or "Proceed Always". In this release, the issue can been corrected and the expected error message displays. (FIRST-15264)
  • If the 
    BlackBerry UEM
     administrator enabled 
    BlackBerry Secure Connect Plus
     with a per-app VPN, activation failed for 
    BlackBerry Dynamics
     apps. (FIRST-15239)
  • When using the file transfer service, if the PDF file name included non-ASCII characters, the PDF file did not open in non-
    BlackBerry Dynamics
     apps. (FIRST-15189)

Known issues

  • WKWebView file upload operations are not secured. Uploaded files are not stored in the device’s secure container. (GD-35772)
  • When using WKWebView, content security policy (CSP) reports are not sent securely. (GD-35170)
  • When using WKWebView, in certain circumstances, OCSP requests are not secured. This issue is related to other security fixes that are in progress. (GD-34491)
  • When using WKWebView, MP4 videos with the H.265/HEVC codec might not play as expected. (GD-34464)
  • When using WKWebView, traffic is not secured when an HTTP Origin header is added to a request or if a content security policy is configured using a Content-Security-Policy header. (GD-33612)
  • When using WKWebView, the JavaScript Fetch API is not secured (requests do not go through 
    Good Proxy
    ). (GD-32483)