BlackBerry Dynamics SDK for iOS

 version 5.0

In the 

BlackBerry Dynamics SDK for iOS

 4.2, the password autofill feature could not be used to unlock 

BlackBerry Dynamics

 apps. In this release, the 

BlackBerry Dynamics SDK

 disables the password autofill feature in all other scenarios as well.

This release of the 

BlackBerry Dynamics SDK for iOS

 introduces a compliance enhancement to protect against malicious attempts to add a debugger to deployed 

BlackBerry Dynamics

 apps. Compliance profiles in 

UEM

 and compliance policies in 

Good Control

 provide the ability to detect when a device OS is jailbroken and to initiate an enforcement action. This feature now extends to deployed 

BlackBerry Dynamics

 apps, compiled with SDK version 5.0, where an active debugging tool is detected. If the detect jailbroken OS compliance setting is enabled, the 

BlackBerry Dynamics Runtime

 stops a 

BlackBerry Dynamics

 app if it detects an active debugging tool. 

Please note that if you want to debug one of your 

BlackBerry Dynamics

 apps in an environment where a compliance profile or compliance policy is applied, the compliance setting to detect jailbroken devices must be disabled.

The setting to detect jailbroken devices is disabled by default in 

UEM

 compliance profiles and enabled by default in standalone 

Good Control

 compliance policies. It is recommended that you test your custom 

BlackBerry Dynamics

 apps in an environment with the detect jailbroken devices setting enabled before you distribute the app in the production environment, to ensure that the app works as expected while this setting is enabled.

This release of the 

BlackBerry Dynamics SDK for iOS

 includes logging changes for enhanced security. You can configure how your 

BlackBerry Dynamics

 apps generate console log information. For more information about console logs controlled by developers and container logs controlled by 

UEM

 or 

Good Control

 administrators, see BlackBerry Dynamics Runtime activity log.

If your app uses SDK version 5.0, and the administrator has turned off “Enable detailed logging for BlackBerry Dynamics apps” in the 

BlackBerry Dynamics

 profile (

UEM

) or security policy (

Good Control

), the app does not generate console log information. This provides additional protection against attacks by malicious users. This change has no impact on how container logs are generated.

The “Enable detailed logging for BlackBerry Dynamics apps” setting is off by default.

For 

BlackBerry Dynamics

 apps running SDK version 5.0 or later, console logs are generated only if this setting is turned on or if the app is running in enterprise simulation mode.

The 

BlackBerry UEM

 version 12.10 release adds support for certificate enrollment using SCEP with 

Entrust

 and 

Microsoft

 NDES for 

BlackBerry Dynamics

 apps. 

UEM

 administrators can configure and assign a SCEP profile for 

BlackBerry Dynamics

 apps in the 

UEM

 management console.

For more information, see “SCEP profile settings” in the UEM Administration Guide. 

This release adds a new GDPushChannel constructor to improve infrastructure performance. The previous GDPushChannel constructor will be deprecated in the next release. For more information, see the GDPushChannel Class Reference.