- 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 client 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 might be asked to provide the log file to the BlackBerry
Dynamics
technical support
team, but this is typically only necessary for complex support issues.