Configure compliance settings so you can debug your app

Compliance profiles in BlackBerry UEM provide the ability to detect when a device OS is jailbroken and to initiate an enforcement action (this option is disabled by default). This feature extends to deployed BlackBerry Dynamics apps, compiled with SDK version 5.0 or later, where an active debugging tool is detected. Your options for configuring this feature depend on the version of BlackBerry UEM and the BlackBerry Dynamics SDK:
  • If your organization uses BlackBerry UEM version 12.11 MR1 or later and the BlackBerry Dynamics SDK version 6.1 or later, when you enable the compliance setting to detect a jailbroken OS, you can configure the setting “Enable anti-debugging for BlackBerry Dynamics apps”. If enabled, the BlackBerry Dynamics Runtime stops a BlackBerry Dynamics app if it detects an active debugging tool. If disabled, the BlackBerry Dynamics Runtime takes no action when it detects an active debugging tool.
  • In UEM versions earlier than 12.11 MR1, the “Enable anti-debugging for BlackBerry Dynamics apps” option is not present and this functionality is enabled by default. If you enable the compliance setting to detect a jailbroken OS, the BlackBerry Dynamics Runtime stops a BlackBerry Dynamics app when it detects an active debugging tool.

If you want to debug a BlackBerry Dynamics app in an environment where a compliance profile is applied, verify that the compliance settings are configured as required. Alternatively, you can use a non-debug build of your app to test it with the compliance settings enabled.