- 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
Link for FIPS in Objective-C or C++
- If you are not using a default xcconfig file, create one nameddefault.xcconfigand configure your build options to use it.
- In your project build settings, verify that the debug and other build configurations point todefault.xcconfig.
- Add the following lines to thedefault.xcconfigfile to ensure that the FIPS canister linking script gd_fipsld is called as part of the build process:FIPS_PACKAGE=$(CURRENT_ARCH).sdk LDPLUSPLUS=$(HOME)/Library/Application Support/BlackBerry/Good.platform/iOS/FIPS_module/$FIPS_PACKAGE/bin/gd_fipsld LD=$(HOME)/Library/Application Support/BlackBerry/Good.platform/iOS/FIPS_module/$FIPS_PACKAGE/bin/gd_fipsld
- Set the deployment target to the required version (see Software requirements).
- In theOther Linker Flagsfield in the target build settings, verify that theall_load linkerflag is not selected.
If your project or app includes at least one
Swift
language source file, see Link for FIPS in Swift.