- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for Face ID
- Support for certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- Requirements
- BlackBerry Dynamics software versions
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Requirements: Frameworks and libraries
- Requirement: URL scheme
- Required build-time declarations: URL type
- Using NSURLSystem for KCD
- GDAssets.bundle required in build phase
- Compatibility with the BlackBerry Dynamics Launcher Library
- App UI restrictions
- Supported and unsupported features on iOS
- Link for FIPS in Objective-C or C++
- Steps to get started with the BlackBerry Dynamics SDK
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps in Objective-C
- BlackBerry Dynamics and the Swift programming language
- Testing and troubleshooting
- Readying your app for deployment: server setup
- Details of support for client certificates
Logging and diagnostics
The processing activity of the
BlackBerry Dynamics Runtime
is logged by the runtime itself. The activity log is written to the BlackBerry
Dynamics
secure container on the device after deployment. 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 or later, and the
UEM
or Good Control
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.