Disable compliance settings so you can debug your app

Compliance profiles in 

BlackBerry UEM

 and compliance policies in standalone 

Good Control

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

BlackBerry Dynamics

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

BlackBerry Dynamics Runtime

 stops a 

BlackBerry Dynamics

 app if it detects an active debugging tool.

If you want to debug one of your 

BlackBerry Dynamics

 apps in an environment where a compliance profile or policy is applied, the compliance setting to detect jailbroken devices must be disabled. Alternatively, you can use a non-debug build of your app to test it with the compliance setting enabled.

The setting to detect jailbroken devices is disabled by default in 

UEM

 compliance profiles and enabled by default in standalone 

Good Control

 compliance policies.