- What is the BlackBerry Dynamics SDK?
- 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
- Replace the default splash screen for inactive apps
- 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
- Enabling microphone and camera support with WebRTC
- Integrating BlackBerry Analytics
- Integrating CylancePERSONA
- Sample apps in Objective-C
- Testing and troubleshooting
- Deploying your BlackBerry Dynamics app
- Deploying certificates to BlackBerry Dynamics apps
Troubleshooting: FIPS
Issue | Possible Solution |
|---|---|
The app crashes | Crashes might occur if the FIPS canister has not been linked to the app correctly. Check for the following line in the log output: "Crypto::initialise: FIPS_mode_set failed: fingerprint does not match" Verify that you followed the steps in Link for FIPS in Objective-C or C++ and, if necessary, Link for FIPS in Swift and that no errors are reported. |
"invalid arch name '-arch armv7s'" linker error when building from Xcode | For development or testing purposes, set Build Active Architecture Only to Yes . For production release, set Build Active Architecture Only to No . |