- What is the BlackBerry Dynamics SDK?
- BlackBerry Dynamics API reference
- Key features of the BlackBerry Dynamics SDK
- Activation
- Secure storage
- Secure communication
- Shared Services Framework
- Data Leakage Prevention
- User authentication
- Administrative controls
- Advanced security features with BlackBerry Protect Mobile
- Data collection and metrics with BlackBerry Analytics
- Dynamic security response with BlackBerry Persona
- Requirements and support for platform-specific features
- Software requirements
- Using an entitlement ID and version to uniquely identify a BlackBerry Dynamics app
- FIPS compliance
- Declaring a URL type to support BlackBerry Dynamics features
- App UI restrictions
- Requirements and prerequisites for iOS platform features
- Supported TLS protocols and cipher suites
- Steps to get started with the BlackBerry Dynamics SDK
- Integrating optional features
- Preventing password autofill in the app UI
- Enforcing local compliance actions
- Adding custom policies for your app to the UEM management console
- Add a watermark to the screens in a BlackBerry Dynamics app
- Allow unencrypted data to be copied to the pasteboard
- Prompt the user to update a BlackBerry Dynamics app
- Adding a custom logo and colors with the branding API
- Using zero sign-on for SaaS services through BlackBerry Enterprise Identity
- Integrating BlackBerry Enterprise Mobility Server services
- Integrating BlackBerry Analytics
- Integrating BlackBerry Persona
- Sample apps in Objective-C
- Testing and troubleshooting
- Deploying your BlackBerry Dynamics app
- Deploying certificates to BlackBerry Dynamics apps
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 the BlackBerry Dynamics Runtime activity log appendix in the API reference (Android/iOS).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.