Configure compliance settings so you can debug your app
Compliance profiles in
BlackBerry UEMprovide the ability to detect when a device OS is rooted and to initiate an enforcement action (this option is disabled by default). This feature extends to deployed
BlackBerry Dynamicsapps, 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 UEMand the
BlackBerry Dynamics SDK:
- If your organization usesBlackBerry UEMversion 12.11 MR1 or later and theBlackBerry Dynamics SDKversion 6.1 or later, when you enable the compliance setting to detect a rooted OS, you can configure the setting “Enable anti-debugging forBlackBerry Dynamicsapps”. If enabled, theBlackBerry Dynamics Runtimestops aBlackBerry Dynamicsapp if it detects an active debugging tool. If disabled, theBlackBerry Dynamics Runtimetakes no action when it detects an active debugging tool.
- InUEMversions 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 rooted OS, theBlackBerry Dynamics Runtimestops aBlackBerry Dynamicsapp when it detects an active debugging tool.
If you want to debug a
BlackBerry Dynamicsapp 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.