BlackBerry Dynamics Bindingsfor Xamarin.iOSDevelopment Guide

7.0

2020-04-07Z

 |  | 2

Contents

What is the BlackBerry Dynamics SDK?............................................................ 5Reliance on the underlying BlackBerry Dynamics SDK....................................................................................... 5BlackBerry Dynamics API reference..................................................................................................................... 5Key features of the BlackBerry Dynamics SDK....................................................................................................5

Activation..................................................................................................................................................... 6Secure storage............................................................................................................................................ 7Secure communication...............................................................................................................................7Shared Services Framework...................................................................................................................... 8Data Leakage Prevention........................................................................................................................... 8User authentication.....................................................................................................................................9Administrative controls............................................................................................................................ 10Advanced security features with CylancePROTECT.............................................................................. 10

Requirements and support for platform-specific features............................... 12Software requirements.........................................................................................................................................12Using an entitlement ID and version to uniquely identify a BlackBerry Dynamics app................................... 12

Relationship between the entitlement ID and version and native identifiers........................................13FIPS compliance...................................................................................................................................................13Declaring a URL type to support BlackBerry Dynamics features..................................................................... 14Requirements and prerequisites for iOS platform features..............................................................................14

Support for Touch ID................................................................................................................................15Support for Face ID.................................................................................................................................. 15Support for WKWebView..........................................................................................................................15Support for the Apple Universal Clipboard............................................................................................. 16Unsupported  iOS features........................................................................................................................16

Steps to get started with the BlackBerry Dynamics SDK..................................17Install the BlackBerry Dynamics bindings for Xamarin.....................................................................................18Developing apps in Microsoft Visual Studio on Windows with the Mac Agent...............................................18Load bindings for a new project.........................................................................................................................19Enable apps to link for FIPS 140-2 compliance................................................................................................ 19Implement a BlackBerry Dynamics event listener............................................................................................. 20Implement the BlackBerry Dynamics Launcher.................................................................................................22

About the BlackBerry Dynamics SDK for Xamarin.Forms.................................23Principal interfaces...............................................................................................................................................23Using the BlackBerry Dynamics SDK for Xamarin.Forms................................................................................. 23

Sample apps................................................................................................... 25

Testing and troubleshooting........................................................................... 26

 |  | iii

Testing with Microsoft Visual Studio................................................................................................................. 26Implementing automated testing for BlackBerry Dynamics Xamarin apps.....................................................26

Automated testing with the BlackBerry Dynamics Xamarin sample apps........................................... 26Preparing for automated testing............................................................................................................. 27Executing automated tests for Android Xamarin apps......................................................................... 27Executing automated tests for iOS Xamarin apps.................................................................................29Executing automated tests for Xamarin.Forms apps............................................................................31

Deploying your BlackBerry Dynamics app....................................................... 33

Deploying certificates to BlackBerry Dynamics apps....................................... 34Using Personal Information Exchange files.......................................................................................................34

Configuring support for client certificates..............................................................................................35Certificate requirements...........................................................................................................................35

Using Kerberos..................................................................................................................................................... 36

Legal notice.................................................................................................... 37

 |  | iv

What is the BlackBerry Dynamics SDK?The BlackBerry Dynamics SDK provides a powerful set of tools that you can use to create secure productivityapps for a BlackBerry UEM or Good Control domain. The SDK leverages the full capabilities of thesecure BlackBerry Dynamics platform, so you can focus on building your apps rather than learning how to secure,deploy, and manage those apps.

The BlackBerry Dynamics SDK is available for all major development platforms. It allows you to leverage manyvaluable services, including secure communication, securing data in file systems and databases, inter-app dataexchange, presence, push, directory lookup, single sign-on authentication, identity and access management, andmore.

This guide will provide:

• Information about supported features• Development requirements and prerequisites• Instructions for installing, configuring, and using the SDK• Considerations for key platform features• Information about the sample apps provided with the SDK• Testing and troubleshooting guidance• Guidance for deploying your app 

This guide is intended for intermediate and experienced developers with an understanding of how to create appsfor the intended platform. It is not a basic tutorial.

Reliance on the underlying BlackBerry Dynamics SDKApps developed with the Xamarin bindings rely on the underlying BlackBerry Dynamics SDK. The full set of theSDK APIs is bound to a C#/.NET counterpart. For example:

 

•  BlackBerry Dynamics SDK for iOS Objective-C:  +(void)initializeWithClassNameConformingToUIApplicationDelegate:(NSString*)applicationDelegate;

•  Xamarin C#/.NET: static voidInitializeWithClassNameConformingToUIApplicationDelegate (stringapplicationDelegate);

BlackBerry Dynamics API referenceThe BlackBerry Dynamics SDK API reference describes the available interfaces, classes, methods, and muchmore. The API reference for each SDK platform is available at https://developers.blackberry.com/us/en/resources/api-reference.html.

Key features of the BlackBerry Dynamics SDKThis section provides more information about key features of the BlackBerry Dynamics SDK. It does not detail thecomplete feature set. For more information about the full list of supported features and APIs, see the BlackBerryDynamics SDK API reference for your platform.

 | What is the BlackBerry Dynamics SDK? | 5

For more information about the requirements and prerequisites to support platform-specific features,see Requirements and support for platform-specific features.

The implementation of some of the features discussed in this section will depend on how the UEM orstandalone Good Control administrator has configured your organization’s servers, network, and otherinfrastructure components. Contact the administrator to clarify whether there are components of a feature thatare configured or managed using the management server.

ActivationInfrastructure and enterprise activation

After a BlackBerry Dynamics app is installed on a user’s device, the user must activate the app in order to useit. The activation process registers the app with the management server and gives the app access to the fullcapabilities of the BlackBerry Dynamics platform. The activation process ensures that all end users are fullyauthorized and permitted to use the app.

Users can activate a BlackBerry Dynamics app manually using an access key provided by the administrator, byusing the UEM Client, or by using the Easy Activation feature described below.

For more information about activating BlackBerry Dynamics apps, see the Activation section in the GDAndroidclass reference or GDiOS class reference and Managing BlackBerry Dynamics apps in the UEM AdministrationGuide.

Easy Activation 

Easy Activation simplifies the process of activating multiple BlackBerry Dynamics apps on a user’s device. WithEasy Activation, a device user only needs to activate the first BlackBerry Dynamics app on their device using anaccess key or the UEM Client; when the user installs additional BlackBerry Dynamics apps, the user can chooseto delegate the activation process to the previously activated app. Any BlackBerry Dynamics app can be anactivation delegate, but priority is given to the app that is configured as the authentication delegate.

Easy Activation is automatically enabled for all BlackBerry Dynamics apps that are produced by BlackBerry. Toenable Easy Activation for your custom BlackBerry Dynamics app, the UEM or standalone GoodControl administrator must specify the app package ID (Android) or bundle ID (iOS) in the BlackBerryDynamics app settings in the management console. Contact your organization’s administrator to provide thisinformation. For instructions for specifying the package ID or bundle ID for an app, see Manage settings for aBlackBerry Dynamics app in the UEM Administration Guide.

On the application side, Easy Activation is enabled by default by the BlackBerry Dynamics Runtime.

For more information, see the Easy Activation section in the BlackBerry Dynamics Security White Paper.

Programmatic activation

The programmatic activation feature enables a BlackBerry Dynamics app to activate without any user interactionand without displaying activation prompts or progress screens. This can be useful when targeting your apps to aconsumer audience or for developing apps for devices that have limited or no means of user input.

For more information about programmatic activation, see programmaticActivityInit in the BlackBerryDynamics SDK for Android API Reference or programmaticAuthorize in the BlackBerry Dynamics SDK for iOSAPI Reference.

Note the following implementation details:

• Decide whether you want users to specify a password to unlock a BlackBerry Dynamics app after the initialactivation. You can use programmatic activation while still requiring users to type a password to unlock theapp. This setting is configured in a BlackBerry Dynamics profile in UEM.

• To activate the app, your application server must use the BlackBerry Web Services REST APIs to retrieve theuser credentials and to generate an access key. You may need to create a new UEM user account or to lookup

 | What is the BlackBerry Dynamics SDK? | 6

an existing user account. See the User resource in the BlackBerry Web Services REST API reference for theavailable REST APIs that can be used to create a user, lookup a user, and to generate an access key.

• Pass the user credentials to the app andcall programmaticActivityInit or programmaticAuthorize with the retrieved credentials,setting ShowUserInterface to false.

• For Android, receive the broadcast event GD_STATE_ACTIVATION_ACTION to track activation progressfrom NotActivated to InProgress to Activated. You can choose to display a progress indicator duringthis short period.

• For iOS, observe GDState.BBActivationState to track activation progressfrom NotActivated to InProgress to Activated. You can choose to display a progress indicator duringthis short period.

• Once activation completes, the user is prompted to set a password (unless you’ve configuredthe BlackBerry Dynamics profile to not require a password). The app should wait forthe GD_STATE_AUTHORIZED_ACTION notification.

• You can use configureUI (Android/iOS) to customize the UI of the password screen (for example, with acustom logo and colors). 

Secure storageSecure file system

BlackBerry Dynamics apps store data in a secure, encrypted file system. For more information,see BlackBerry Dynamics File I/O Package in the BlackBerry Dynamics SDK for Android API reference,or GDFileManager and GDFileHandle in the BlackBerry Dynamics SDK for iOS API reference.

Core data

BlackBerry Dynamics apps can store Core Data objects in a secure, encrypted store. For more information,see GDPersistentStoreCoordinator in the API reference.

Secure SQL database

BlackBerry Dynamics apps can leverage a secure SQL database that stores and encrypts data on the user’sdevice. The secure SQL database is based on the SQLite library.

For more information, see the BlackBerry Dynamics SQL Database page in the BlackBerry Dynamics SDK APIreference (Android/iOS).

Secure communicationThe BlackBerry Dynamics platform enables secure data exchange between a BlackBerry Dynamics app onan end user’s device and a back-end application server on the Internet or behind the enterprise firewall. Anycommunication through the enterprise firewall uses the secure BlackBerry Dynamics proxy infrastructure. Oneapp can communicate with multiple application servers.

To learn more about the programming interfaces for secure communication, see GDSocket and GDHttpClient inthe BlackBerry Dynamics SDK for Android API reference, or GDSocket, GDURLLoadingSystem, and NSURLSessionSupport in the BlackBerry Dynamics SDK for iOS API reference.

AppKinetics

AppKinetics, or Inter-Container Communication (ICC), is a method for securely exchanging data and commandsbetween two BlackBerry Dynamics apps on the same device. The exchange uses a consumer-provider model: oneapp initiates a service request that the other app receives and responds to as a service provider.

For more information about AppKinetics, see the Inter-Container Communication Package in the BlackBerryDynamics SDK for Android API reference, or GDService and GDServiceClient in the BlackBerry Dynamics SDK foriOS API reference. 

 | What is the BlackBerry Dynamics SDK? | 7

Shared Services FrameworkBlackBerry Dynamics apps can communicate with each other and application servers using the Shared ServicesFramework, a collaboration system that is defined by two components: one that provides a service and anotherthat consumes the service.

The provider can be a client-side service, which is a BlackBerry Dynamics app that uses the GDServiceAPIs (Android/iOS), or a server-side service that is provided by an application server or other remote system. Theservice is consumed by a BlackBerry Dynamics app that communicates with the provider using AppKinetics (aproprietary BlackBerry ICC protocol) for client-side services or a protocol such as HTTPS for server-side services.

The typical steps that are required to consume a service:

1. Service discovery: The BlackBerry Dynamics app (the consumer) queries for service providers usingthe GDAndroid.getServiceProvidersFor API or the GDiOS.getServiceProvidersFor API. Service discovery isoptional but recommended for both types of services because it respects user entitlements and permissions.

2. Provider selection: The consuming app selects the provider. This is handled by the app code.3. Service request: The consuming app sends a service request to the provider using the GDServiceClient

API (Android/iOS) for client-side services or TCP sockets or HTTP over BlackBerry Dynamics securecommunication (Android/iOS) for server-side services.

4. Service response: The consuming app receives the provider response using the same interface that was usedfor the request (the GDServiceClient API (Android/iOS) for client-side services or BlackBerry Dynamics securecommunication (Android/iOS) for server-side services). 

Client-side services can be used offline and are ideal if the service requires specific user interaction.

Server-side services can be provided by a clustered application server and are ideal if the server software alreadyexists outside of the BlackBerry Dynamics platform.

Client-side and server-side services both require user entitlement in the UEM or standalone GoodControl management console.

If you want your custom BlackBerry Dynamics app to use the Shared Services Framework, the UEM orstandalone Good Control administrator must specify the app package ID (Android) or bundle ID (iOS) inthe BlackBerry Dynamics app settings in the management console. Contact your organization’s administratorto provide this information. For instructions for specifying the package ID or bundle ID for an app, see Managesettings for a BlackBerry Dynamics app in the UEM Administration Guide.

Sample apps that are included with the SDK demonstrate how to use the Shared Services Framework. For moreinformation about how to use the Shared Services Framework, see the following resources:

• GDAndroid.getServiceProvidersFor• GDiOS.getServiceProvidersFor• GDService (Android/iOS)• GDServiceClient (Android/iOS) • BlackBerry Dynamics Service Definition (Android/iOS)• Definitions and descriptions of published services

Server-side services can use the Push Channel API (Android/iOS) to send notifications to BlackBerryDynamics apps. The channel is end-to-end secure at the same level as BlackBerry Dynamics securecommunication. As a result, the BlackBerry Dynamics app does not need to poll the application server, whichdecreases the load on both the app and the application server. Any application server that is a service providercan use the Push Channel.

Data Leakage PreventionThe BlackBerry UEM or standalone Good Control administrator can use Data Leakage Prevention (DLP)settings in BlackBerry Dynamics profiles (UEM) or security policies (Good Control) to configure data protection

 | What is the BlackBerry Dynamics SDK? | 8

standards, including enabling or disabling copy and paste between BlackBerry Dynamics apps and non-BlackBerryDynamics apps, screen captures, dictation, FIPS, and more.

Contact your organization’s administrator to configure DLP standards as necessary for your custom BlackBerryDynamics apps.

User authenticationBlackBerry UEM and standalone Good Control offer the following options to adjust the user experience foraccessing BlackBerry Dynamics apps.

Fingerprint and biometric authentication

Various forms of biometric authentication are supported by the BlackBerry Dynamics SDK, including fingerprintauthentication and for Android and Touch ID and Face ID for iOS. The BlackBerry UEM or standalone GoodControl administrator can use a BlackBerry Dynamics profile (UEM) or a security policy (Good Control) to enablebiometric authentication. Contact your organization’s administrator to enable and configure these features.

For more information, see BlackBerry Dynamics and Fingerprint Authentication.

Authentication delegation

The BlackBerry UEM or standalone Good Control administrator can configure up to three BlackBerryDynamics apps on users’ devices to act as an authentication delegate (a primary, secondary, and tertiarydelegate). When a user opens any BlackBerry Dynamics app, the device will display the login screen of theauthentication delegate app. After the user logs in successfully, all of the BlackBerry Dynamics apps on the deviceare unlocked. The user does not need to enter a password again until the idle timeout is reached.

If you want your custom BlackBerry Dynamics app to be an authentication delegate, the UEM or standalone GoodControl administrator must specify the app package ID (Android) or bundle ID (iOS) in the BlackBerryDynamics app settings in the management console. Contact your organization’s administrator to provide thisinformation. For instructions for specifying the package ID or bundle ID for an app, see Manage settings for aBlackBerry Dynamics app in the UEM Administration Guide.

The administrator configures one or more authentication delegate using a BlackBerry Dynamics profile (UEM)or a security profile (Good Control). It is a best practice to configure the most commonly used app as theauthentication delegate. Contact your organization’s administrator to configure one or more authenticationdelegates.

Note: If the administrator configures a secondary authentication delegate, the administrator must notify usersthat if they delete the primary authentication delegate app, the user must unlock the secondary delegate app andset the app password again so that it can be used to authenticate any additional BlackBerry Dynamics apps. Thesame requirement applies if a tertiary delegate is configured and the primary and secondary delegate apps aredeleted.

Do not require a password

Enabled using a BlackBerry Dynamics profile (UEM) or security policy (Good Control), this setting removes thepassword login for BlackBerry Dynamics apps. Users cannot choose whether to use a password.

Do not enable authentication delegation and this setting in the same profile or policy set. This feature issupported in UEM 12.7 or later and Good Control 3.0.50.70 or later. If the setting is enabled and then disabled at alater date, users are prompted to create a password the next time they log in to a BlackBerry Dynamics app.

You can use the GDAndroid.getInstance().canAuthorizeAutonomously() or [GDiOSsharedInstance].canAuthorizeAutonomously method to check if this feature is enabled. See the GDInteractionsample app (Android) or the SecureStore sample app (iOS) for examples of this method.

Bypass the app unlock screen

 | What is the BlackBerry Dynamics SDK? | 9

Enabled in the UEM Client settings for a specific BlackBerry Dynamics app (UEM) or by using an app policy (GoodControl), this setting allows an app to completely bypass the password login screen.

For more information and programming guidance, see the Bypass Unlock Developer Guide.

Background Authorize

Background Authorize is a restricted API that allows a recently locked BlackBerry Dynamics app to use theprincipal BlackBerry Dynamics APIs (such as secure storage and secure communication) when the app is runningin the background.

This feature can be useful in scenarios where the app has stopped unexpectedly and is started in the backgroundin response to an APNS message (for example, a new email). If Background Authorize is enabled, the app candownload new data and store it in the secure container. When the user brings the app to the foreground they canauthorize and immediately access the data (for example, messages).

To access this restricted API, submit a request to the BlackBerry Dynamics Registrar programat BlackBerryDynamicsRegistrar@blackberry.com.

For more information about this feature, see the Background Authorize Developer Guide.

Administrative controlsThe BlackBerry UEM or standalone Good Control administrator can use various server settings, policies, andprofiles to manage BlackBerry Dynamics apps and ensure that app usage meets the organization’s securitystandards. Consult with your organization’s administrator to ensure that your custom apps adhere to theconfigured settings in the management console.

For more information, see Controlling BlackBerry Dynamics on users devices, Enforcing compliance rules fordevices, and Managing BlackBerry Dynamics apps in the UEM Administration Guide. If your organization usesstandalone Good Control, see the Good Control Online Help.

You also have the option to add new management policies and settings that are specific to yourcustom BlackBerry Dynamics app to the UEM management console so that they can be configured andapplied to users by UEM administrators. For more information, see Adding custom policies for your app tothe UEM management console.

Advanced security features with CylancePROTECTThe BlackBerry Dynamics SDK integrates the CylancePROTECT library to support CylancePROTECT forBlackBerry UEM. CylancePROTECT is a licensed service that offers a suite of features that enhances BlackBerryUEM’s ability to detect, prevent, and resolve security threats without disrupting the productivity of yourworkforce. CylancePROTECT is configured and managed by the BlackBerry UEM administrator. No additionaldevelopment or integration effort is required if your organization wants to leverage the CylancePROTECT featuresfor custom BlackBerry Dynamics apps.

CylancePROTECT uses a combination of advanced technologies, including:

• The cloud-based CylanceINFINITY service that uses sophisticated AI and machine learning to identify malwareand unsafe URL

• The UEM server that provides a complete device management and compliance infrastructure for yourorganization

• BlackBerry apps that monitor and enforce security standards at the device and user level

The seamless integration of these technologies establishes a secure ecosystem where data is protected andmalicious activities are identified at all endpoints and eliminated proactively.

CylancePROTECT includes the following features:

 | What is the BlackBerry Dynamics SDK? | 10

• Malware detection for apps (including BlackBerry Dynamics apps) that are uploaded to UEM for internaldeployment

• Malware detection on Android devices• Sideloaded app detection on iOS devices• Safe browsing with BlackBerry Dynamics apps• Integrity checking for BlackBerry Dynamics apps on iOS devices using the Apple DeviceCheck framework• Hardware certificate attestation for BlackBerry Dynamics apps on Android devices

For more information about CylancePROTECT, see the CylancePROTECT documentation.

 | What is the BlackBerry Dynamics SDK? | 11

Requirements and support for platform-specific featuresThis section provides the software requirements for using the SDK, as well as prerequisites that are required tosupport platform-specific features.

Software requirements

Item Requirement

Xamarin software license Community, Professional, or Enterprise

BlackBerry Dynamics SDK foriOS

Latest available version of the BlackBerry Dynamics SDK for iOS

Deployment target iOS 12 or later

iOS SDK 12.0 or later

Xamarin.iOS 13.14.1.39 or later

Microsoft VisualStudio for macOS

8.5 or later

macOS 10.13 or later

Xcode 10 or later

Xcode 10 is still supported but will be deprecated in the next major release.Launcher samples require Xcode 10.2 or later.

Compatibility with previousreleases of the BlackBerryDynamics Bindings forXamarin.iOS

This release of the BlackBerry Dynamics Bindings for Xamarin.iOS is notcompatible with the previous releases due to new requirements for iOS 13.

Character encoding for buildfiles

Build files (for example, settings.json) must use UTF-8 character encoding.Verify that the editor that you plan to use does not add non UTF-8 charactersor headers. In general, Java does not work with UTF-8- BOM (byte order mark).

Note: The key prefix "blackberry" is reserved by BlackBerry and should not be used for key values, key attributes,or key elements. For more information and examples, see the Application Policies Definition in the appendix of theAPI Reference.

Using an entitlement ID and version to uniquely identify a BlackBerryDynamics appBlackBerry Dynamics apps are uniquely identified by a BlackBerry Dynamics entitlement ID (GDApplicationID) andentitlement version (GDApplicationVersion). The entitlement ID and entitlement version are used to manage end-

 | Requirements and support for platform-specific features | 12

user entitlement in the BlackBerry UEM or standalone Good Control management console. The values are alsoused for app publishing and service provider registration.

These values are specified in the assets/settings.json file for Android or in the Info.plist file for iOS.

You must define both the entitlement ID and the entitlement version for all of your BlackBerry Dynamics apps,regardless of whether you use the Shared Services Framework. The same entitlement ID must be used torepresent the app across all platforms.

For more information about setting and checking the entitlement ID and version, the proper format to use forthese values, and other requirements and considerations:

• See the GDAndroid Class reference in the BlackBerry Dynamics SDK for Android API Reference, especiallythese sections:

• Identification• Indirect Authorization Initiation• void authorize (GDAppEventListener eventListener ) throws GDInitializationError 

• See the GDiOS Class reference in the BlackBerry Dynamics SDK for iOS API Reference, especially thesesections:

• Identification• Authorization• - (void) authorize: (id< GDiOSDelegate > _Nonnull) delegate 

Relationship between the entitlement ID and version and native identifiersThe entitlement ID (GDApplicationID) and entitlement version (GDApplicationVersion) of a BlackBerryDynamics app are different from the native identifiers that are required by the app OS platform. The nativeidentifiers for Android are the packageName and packageVersion values in the AndroidManifest.xml file. Thenative identifiers for iOS are the CFBundleIdentifier and CFBundleVersion in the Info.plist file. The values of theentitlement ID and entitlement version and the platform native identifiers can be the same, but do not have to be.

To take advantage of BlackBerry Dynamics features such as Easy Activation, authentication delegation, certificatesharing, the Shared Services Framework, and more, the UEM or standalone Good Control administratormust specify the entitlement ID and version and the native identifier (package name or bundle ID) for acustom BlackBerry Dynamics app in the management console. For more information, see Add an internalBlackBerry Dynamics app entitlement and Manage settings for a BlackBerry Dynamics app in the UEMAdministration Guide, or the Good Control Help.

The native identifiers for your custom BlackBerry Dynamics app should be unique, especially with respect to appsthat are available through public app stores. Duplicate native identifiers can prevent the proper installation orupgrade of an app.

You must change the native app version if you want to distribute a new version of the app. You only need tochange the entitlement version if the app starts to provide a new shared service or shared service version, or if theapp stops providing a shared service or shared service version.

FIPS complianceIt is a best practice to make your BlackBerry Dynamics apps compliant with U.S. Federal Information ProcessingStandards (FIPS) 140-2.The BlackBerry Dynamics SDK distribution contains FIPS canisters and tools.

The BlackBerry UEM or standalone Good Control administrator enables FIPS compliance using a BlackBerryDynamics profile (UEM) or security policy (Good Control). If enabled, BlackBerry Dynamics apps must startin FIPS-compliant mode. The SDK determines whether a service is running in FIPS mode when the appcommunicates with the server to receive policies.

 | Requirements and support for platform-specific features | 13

FIPS compliance enforces the following constraints:

• The use of MD4 and MD5 are prohibited. As a result, access to NTLM-protected or NTLM2-protected webpages and files is blocked.

• In secure socket key exchanges with ephemeral keys, with servers that are not configured to use Diffie-Hellman keys of sufficient length, BlackBerry Dynamics retries with static RSA cipher suites. 

Note:

• When you enable FIPS compliance, user certificates must use encryption that meets FIPS standards. If a usertries to import a certificate with encryption that is not compliant, the user receives an error message indicatingthat the certificate is not allowed and cannot be imported.

• For iOS, when you build for testing with the x86 64-bit simulator, FIPS mode is not enforced. As a result, youmight see a difference in behavior with the simulator compared to actual operation. BlackBerry recommendsthat you always test your app on actual iOS hardware and not rely exclusively on the simulation.

Declaring a URL type to support BlackBerry Dynamics featuresA BlackBerry Dynamics app for iOS devices must declare a URL type so that it can be discovered by other apps onthe same device. This enables AppKinetics, which is required for many BlackBerry Dynamics features. The URLtype and schemes are declared in the app's Info.plist file.

The URL type must be the same as the app's native bundle ID. Within the URL type declaration,the following URL schemes must be declared. For example, if the native bundle ID of the appis com.example.gd.myapp and its entitlement version (GDApplicationVersion) is 1.0.0.0, then the declared URLtype is com.example.gd.myapp and the schema declarations are as follows:

Format Description Example

com.good.gd.discovery Always required Exactly as shown

com.good.gd.discovery.

enterprise

Always required  Exactly as shown

<bundle_ID>.

sc3

Always required com.example.gd.myapp.sc3

<bundle_ID>.

sc2

Enables an app touse authentication delegation andis required for all BlackBerryDynamics apps

com.example.gd.myapp.sc2

<bundle_ID>.

sc2.<GDApplicationVersion>

Required only if your app providesa discoverable service

com.example.gd.myapp.sc2.

1.0.0.0

Requirements and prerequisites for iOS platform featuresThis section provides specific requirements or considerations to support features of the iOS platform inyour BlackBerry Dynamics apps.

 | Requirements and support for platform-specific features | 14

Support for Touch IDTouch ID is a fingerprint recognition system for some iOS devices.

Touch ID can be allowed for user authentication in BlackBerry Dynamics apps in addition to standard passwordauthentication. For more information about Touch ID, see BlackBerry Dynamics and Fingerprint Authentication inthe BlackBerry Developers for Enterprise Apps portal.

Support for Face IDThe BlackBerry Dynamics SDK for iOS version 4.0 and later supports Face ID. An administrator can enable ordisable the feature in a BlackBerry Dynamics profile in UEM or in a security policy in Good Control.

ach app must add the NSFaceIDUsageDescription key to the Info.plist file. For more details about Face ID, seethe Build-Time Configuration appendix in the API Reference.

Support for WKWebViewThe BlackBerry Dynamics SDK for iOS version 4.2 and later supports secure WKWebView for displaying interactiveweb content.

Note the following support details:

• The SDK supports multiple WKWebView instances. The instances must be created programmatically.• The SDK supports loading WKWebView from UIStoryBoard. To avoid any possible data leaks, you must

load UIStoryBoard with the WKWebView component after the SDK is initialized.• The supported versions of iOS require JavaScript injection by the BlackBerry Dynamics Runtime.• The secure Fetch API is supported.• Synchronous XMLHttpRequests are supported for iOS 12.2 and later, but the GET method is supported

for iOS 13.1 and later only.

The SDK’s implementation of secure WKWebView currently supports:

• Loading HTTP and HTTPS data• Redirection• Basic, Digest, NTLM, Kerberos, and ClientCertificate authentication• Cookies• Video and audio playback• Asynchronous XHR requests• HTML5 non-persistent local storage• Sending the following types of body data using XMLHttpRequest: ArrayBuffer, Blob, FormData,

URLSearchParams, USVString

The SDK’s implementation of secure WKWebView does not currently support:

• Secure WKWebView creation from UIStoryBoard, including WKWebView controls that are added withthe Xcode Interface Builder tool

• The JavaScript sendBeacon API• The following Data Leakage Prevention (DLP) settings from BlackBerry UEM or standalone Good Control for

long-press or 3D touch actions:

• Do not allow copying data from BlackBerry Dynamics apps into non BlackBerry Dynamics apps• Do not allow copying data from non BlackBerry Dynamics apps into BlackBerry Dynamics apps

• HTML5 persistent local storage• HTML attributes for a link tag (for example, preconnect)• WebSockets• HTTP/2

 | Requirements and support for platform-specific features | 15

Support for the Apple Universal ClipboardThe SDK supports secure cut, copy, and paste operations using the Apple Universal Clipboard. Users cancopy and move data between BlackBerry Dynamics apps and devices that follow Apple Continuity systemrequirements. The apps and devices must be activated for the same user account on the same instanceof BlackBerry UEM or standalone Good Control.

For more information about the Apple Universal Clipboard, see support.apple.com to read Set up UniversalClipboard.

Unsupported iOS featuresThe following features are not supported by the BlackBerry Dynamics SDK:

Feature

 

Details

BitCode BitCode is an intermediate, architecture-independent binary object formatthat allows developers to submit a "machine neutral" app to Apple for afinal, architecture-dependent build. The intermediate nature of BitCode isnot compatible with the cryptographic requirements of the BlackBerryDynamics SDK, which relies on the delivery of libraries or other modules thatare cryptographically signed at build-time. The signatures of the libraries andmodules are validated at runtime to ensure integrity.

If you enable BitCode and try to build an app, a build error will indicate that theSDK does not support BitCode. 

App Extensions  The BlackBerry Dynamics SDK does not support app extensions such asSirikit.

 | Requirements and support for platform-specific features | 16

Steps to get started with the BlackBerry Dynamics SDKStep

 

Action

Download and install the BlackBerry Dynamics Bindings for Xamarin.iOS and the BlackBerryDynamics SDK for iOS. 

If applicable, see Developing apps in Microsoft Visual Studio on Windows withthe Mac Agent.

If applicable, load bindings for a new project.

Enable apps to link for FIPS 140-2 compliance.

Optionally, implement an event listener.

For more information about an alternative method to implement the life cycle of events, see"Add the event-handler skeleton using notifications" in the BlackBerry Dynamics SDK for iOSDevelopment Guide. The GreetingsServer sample app demonstrates this alternative.

Optionally, implement the BlackBerry Dynamics launcher.

Consult the appropriate BlackBerry Dynamics SDK API reference for instructions forimplementing the desired features of the BlackBerry Dynamics platform.

See the sample apps included in the SDK package for examples of how to implement keyfeatures.

If you want to use Xamarin.Forms, see About the BlackBerry Dynamics SDK forXamarin.Forms and the corresponding API reference. 

Test and debug your app.

Deploy your app.

Optionally, deploy certificates to the BlackBerry Dynamics apps on users’ devices.

 | Steps to get started with the BlackBerry Dynamics SDK | 17

Install the BlackBerry Dynamics bindings for XamarinThe bindings are delivered as Dynamic Link Libraries (DLL). The package includes Xamarin projects forthe BlackBerry Dynamics bindings, for each of the sample apps, and for the BlackBerry Dynamics LauncherLibrary.

Before you begin: Visit BlackBerry Developer Downloads to download the BlackBerry Dynamics Bindingspackage for the desired platform. When you click the link, you are prompted to log in to the Developer site withyour BlackBerry Online Account. If you don’t already have an account, you can register and create one.

1. Extract the contents of the BlackBerry Dynamics Bindings SDK package (the projects for the bindings package,sample apps, and if desired, BlackBerry Dynamics Launcher Library).

2. Install the BlackBerry Dynamics SDK for iOS. For instructions, see the BlackBerry Dynamics SDK DevelopmentGuide.

After you finish: It is a best practice to use the binding project (DLL) that is included with every sample appinstead of creating your own binding project.

Developing apps in Microsoft Visual Studio on Windows withthe Mac AgentIf you want to develop apps on a Windows computer using Microsoft Visual Studio with the Mac Agent, visitthe Xamarin development site and follow the instructions in Pair to Mac for Xamarin.iOS development.

The following table provides solutions for common issues when setting up the Mac Agent:

Problem Solution

The project doesn't run in Visual Studio after you addthe ld file to the project folder and mtouch argumentsto the project file.

In your mtouch arguments,change B ${ProjectDir}” to -B/<path_to_project_with_ld_file>" (for example, -B /Users/USER_1/Documents/Projects/iOS/Examples/GreetingsClient").

The Mac Agent does not connect as expected. 1. In Visual Studio on the Windows computer,open Tools > Options > Xamarin > iOS Settings.

2. Click Find Xamarin Mac Agent.3. Enter the name or IP address of

the Mac computer.4. Open the project in Visual Studio on

the Windows computer and run it.5. Close the project and open Tools > Options >

Xamarin > iOS Settings.6. Select the Remote Simulator to

Windows check box to show the simulator onthe Windows computer. If you want to run thesimulator on the Mac computer, do not select thisoption.

7. Run the project again.

 | Steps to get started with the BlackBerry Dynamics SDK | 18

Problem Solution

You get the following exception when the Mac Agentis connecting:

"Could not authenticate the user 'user' with SSH keys.Please check that both $HOME folder and ~/.ssh/authorized_keys have the appropiate permissions touse SSH…”

See the following resources on the Xamarindevelopment site:

• Connection Troubleshooting• Unable to connect to Xamarin Mac Agent

If the solutions at the links above do not work, renameor delete ~/.ssh and try to connect again.

You experience build and deployment errors. See the "Troubleshooting Build and DeploymentErrors" on the Connection Troubleshooting page.

Load bindings for a new projectIf you are starting a new project that has not already been configured for the BlackBerry Dynamics bindingsfor Xamarin, you must configure the project to load them.

1. In Microsoft Visual Studio, open your project.2. Right-click the References folder and click Edit References.3. On the .Net Assembly tab, click Browse and navigate to the uncompressed package with the appropriate DLL

for your platform.4. Follow the prompts to add the DLL to your project.

Enable apps to link for FIPS 140-2 complianceTo meet FIPS 140-2 compliance, all apps must be linked with the linkers provided in the BlackBerry Dynamics SDKfor iOS.

1. In Xamarin Studio, open your BlackBerry Dynamics-enabled Xamarin.iOS project.2. In the project settings, select properties and navigate to Project Options > Build > iOS Build > Code generation

and runtime > Linker behavior.3. Select Link Framework SDKs Only.4. In the Additional mtouch arguments field, specify the following:

--cxx --registrar:static --gcc_flags="-lc++ -B ${ProjectDir}"

Note: The project location (ProjectDir) that you specify should not contain special characters or spaces. Ifyou do include special characters or spaces, they must be escaped. The mtouch arguments above are only asample and should be modified for your needs.

5. Click Save. Note that more advanced examples of mtouch arguments can be found in the sample applications.6. In the same location as your .csproj file, paste a copy of the ld file that is included with every sample app.

After you finish: If you installed the BlackBerry Dynamics SDK for iOS in any location other than the default,edit the ld file in your project and in the sample apps to point to the SDK installation path. Change the value ofthe GD_SDK variable to the absolute install path.

 | Steps to get started with the BlackBerry Dynamics SDK | 19

Implement a BlackBerry Dynamics event listenerThe Application object manages the app’s global app state. Many of the sample apps that are included withthe BlackBerry Dynamics Bindings demonstrate the event handling lifecycle. This topic demonstrates oneapproach to implementing the lifecycle of events.

Before you begin: Define the BlackBerry Dynamics entitlement ID and entitlement version for your app.

1. Include the following code at the top of your AppDelegate.cs file to implement askeleton GDiOSDelegate interface, set the app’s window as a GDWindow (this example relies ona _started boolean variable), use GDAppEvent to process events, and move the app launch codefrom FinishedLaunching to the HandleEvent handler method.

//AppDelegate.cs using System; using UIKit; using Foundation; using System.Diagnostics using GoodDynamics; namespace MyApplication { // The UIApplicationDelegate for the application. This class is responsible for launching the // User Interface of the application, as well as listening (and optionally responding) to application // events from iOS. [Register ("AppDelegate")] public class AppDelegate : GDiOSDelegate { private bool _started; public GDiOS GDLibrary { get; private set; } public NSMutableArray Providers {get; set;} public override UIWindow Window { get; set; } public override bool FinishedLaunching (UIApplication application, NSDictionary launchOptions) { GDLibrary = GDiOS.GDSharedInstance; GDLibrary.Delegate = this; GDLibrary.Authorize(); Window = UIApplication.SharedApplication.Delegate.GetWindow(); Window.MakeKeyAndVisible (); return true; } public override void HandleEvent (GDAppEvent anEvent) { switch (anEvent.Type) { case GDAppEventType.Authorized: OnAuthorized (anEvent); break; case GDAppEventType.NotAuthorized: OnNotAuthorized (anEvent); break; case GDAppEventType.RemoteSettingsUpdate: //handle app config changes break;

 | Steps to get started with the BlackBerry Dynamics SDK | 20

case GDAppEventType.ServicesUpdate: Debug.WriteLine ("Received Service Update Event"); OnServiceUpdate (anEvent); break; default: Debug.WriteLine ("Event Not Handled"); break; } }... }}

2. Verify that your app can handle problems such as authorization errors or actions like remote wipe, lockout, orblocking events. Implement these events in the OnNotAuthorized function.

private void OnNotAuthorized(GDAppEvent anEvent){ switch (anEvent.Code) { case GDAppResultCode.ErrorActivationFailed: case GDAppResultCode.ErrorProvisioningFailed: case GDAppResultCode.ErrorPushConnectionTimeout: case GDAppResultCode.ErrorSecurityError: case GDAppResultCode.ErrorAppDenied: case GDAppResultCode.ErrorAppVersionNotEntitled: case GDAppResultCode.ErrorBlocked: case GDAppResultCode.ErrorWiped: case GDAppResultCode.ErrorRemoteLockout: case GDAppResultCode.ErrorPasswordChangeRequired: Console.WriteLine ("OnNotAuthorized {0}", anEvent.Message); break; case GDAppResultCode.ErrorIdleLockout: break; default: Debug.Assert (false, "Unhandled not authorized event"); break; }}

3. On authorization, start the app. Initialize and start the app UI with the OnAuthorized function.The GDAppResultCode.ErrorNone event is returned by the BlackBerry Dynamics Runtime when a containeris opened and no error occurs (you can test for it as an alternative to the boolean _started shown here).

private void OnAuthorized(GDAppEvent anEvent) { switch (anEvent.Code) { case GDAppResultCode.ErrorNone: if (!_started) { _started = true; //Launch Application UI Here } break; default: Debug.Assert (false, "Authorized startup with an error"); break; } } }

 | Steps to get started with the BlackBerry Dynamics SDK | 21

Implement the BlackBerry Dynamics LauncherYou have the option to implement the BlackBerry Dynamics Launcher, an intuitive front-end UI that makes it easyfor device users to access and modify settings for BlackBerry Dynamics apps. For more information, see thedocumentation for the BlackBerry Dynamics Launcher Framework.

To implement the BlackBerry Dynamics Launcher, you add the BlackBerry Dynamics Launcher button to an activityand include its authentication logic in the appropriate place in your app.

Note: If you want to create your own version of the BlackBerry Dynamics Bindings for Xamarin with customchanges, open the Xamarin Launcher Bindings library project GoodDynamics.iOS.Launcher and check thereference to the Launcher library from the framework path (for example, on Mac the default location is ~/Library/Application/Support/BlackBerry/Good.platform/iOS/Frameworks/Launcher.framework). Look for it under NativeReferences in the solution explorer.

1. Download the BlackBerry Dynamics Launcher software from BlackBerry Developer Downloads.2. Unzip the packages. Copy Launcher.framework to ~/Library/Application/Support/BlackBerry/Good.platform/

iOS/Frameworks (next to GD.framework).3. In your IDE, load the bindings into the desired projects. For each project, right-click References and click Edit

References to reference the Launcher project.4. Add the BlackBerry Dynamics Launcher button and initialize it with the following lines in

the OnAuthorized method of your AppDelegate:

. . . var launcher = new GoodDynamics.iOS.Launcher.GTLauncherViewController(root); Window.RootViewController = launcher; launcher.StartServicesWithOptions(GoodDynamics.iOS.Launcher.GTLauncherServicesStartupOptions.InternalGDAuthTokenAndPushConnectionManagement); ...

Here is a complete example of OnAuthorized with the BlackBerry Dynamics Launcher code inthe case statement: 

...private void OnAuthorized(GDAppEvent anEvent) { switch (anEvent.Code) { case GDAppResultCode.ErrorNone: UINavigationBar.Appearance.TintColor = UIColor.FromRGBA(52f / 255f, 69f / 255f, 84f / 255f, 1); UINavigationBar.Appearance.SetTitleTextAttributes(new UITextAttributes() { TextColor = UIColor.FromRGBA(33f / 255f, 50f / 255f, 65f / 255f, 1) }); var root = new UINavigationController(new ProductsView()); var launcher = new GoodDynamics.iOS.Launcher.GTLauncherViewController(root); Window.RootViewController = launcher; launcher.StartServicesWithOptions (GoodDynamics.iOS.Launcher.GTLauncherServicesStartupOptions.InternalGDAuthTokenAndPushConnectionManagement); Window.MakeKeyAndVisible(); break; default: Debug.Assert (false, "Authorized startup with an error"); break; } }...

 | Steps to get started with the BlackBerry Dynamics SDK | 22

About the BlackBerry Dynamics SDK for Xamarin.FormsXamarin.Forms is a framework that developers can use to create user interfaces that can be used acrossplatforms. For more information, visit developer.xamarin.com to see Getting Started with Xamarin.Forms and AnIntroduction to Xamarin.Forms.

Visit BlackBerry Developer Downloads to download the BlackBerry Dynamics SDK for Xamarin.Forms package.See the BlackBerry Dynamics SDK for Xamarin Release Notes to review the lists of fixed and known issues in eachrelease.

Principal interfacesThe SDK provides a unified API that supports the following principal interfaces:

• Runtime Object• Secure Storage

• Secure SQL Database• Secure File System

• Secure Communication

• Socket• HTTP Communication

• Push Channel• Inter-Application Data Exchange• Single Sign-On

For complete details about each interface, see the BlackBerry Dynamics SDK for Xamarin.Forms API reference.

Using the BlackBerry Dynamics SDK for Xamarin.Forms• Follow the requirements, prerequisites, and setup instructions for the BlackBerry Dynamics SDK for Android or

the BlackBerry Dynamics SDK for iOS (or both, if you develop apps for both platforms).• Follow the instructions in Steps to get started with the BlackBerry Dynamics Bindings for Xamarin.• Use the following Xamarin.Forms libraries that are distributed in the SDK package:

• Xamarin.Forms common libraries:

• BBDXamarinForms.Common.Interfaces.dll• BBDXamarinForms.Common.Library.dll• BBDXamarinForms.Common.Utils.dll

• Xamarin.Forms platform libraries:

• BBDXamarinForms.Droid.Interfaces.dll• BBDXamarinForms.Droid.Library.dll• BBDXamarinForms.iOS.Interfaces.dll• BBDXamarinForms.iOS.Library.dll

• Xamarin binding libraries:

• GoodDynamics.Android.dll• GoodDynamics.iOS.dll

 | About the BlackBerry Dynamics SDK for Xamarin.Forms | 23

• Review the sample projects in the BlackBerry Dynamics SDK for Xamarin.Forms package to familiarizeyourself with the project structure and configurations.

• BlankApp: The main project that contains application views that render on both platforms and allow theexecution of the unified API. Demonstrates how to implement the BlackBerry Dynamics SDK event handlinglifecycle. See the App.xaml.cs file and Implementing a BlackBerry Dynamics event listener.

• AppKinecticsService: Demonstrates how to write a server application that uses the BlackBerry DynamicsInter-Container Communications API (AppKinetics). AppKinetics allows BlackBerry Dynamics apps runningon the same device to exchange data and commands securely.

• SampleAppSuite: Demonstrates how to use the rest of the available APIs.

Note that the sample apps require the following NuGet packages that can be obtained using Microsoft VisualStudio: AutoMapper, NLog, Unity, SQLite-net, and System.ValueTuple.

 | About the BlackBerry Dynamics SDK for Xamarin.Forms | 24

Sample appsThe easiest way to get started with the BlackBerry Dynamics Bindings for Xamarin is to open one of the projectsfor sample apps. Uncompress the desired sample and double-click either the .csproj or .sln file to open theproject.

Sample app Description

AppKinetics shared services Provides examples of how to use the BlackBerry Dynamics Shared ServicesFramework.

Core data Demonstrates how to use BlackBerry Dynamics with a Core Data IncrementalData Store backed by an encrypted SQLite database. The sampledemonstrates how Core Data can be used to securely store a list of productsand their prices.

Remote DB Demonstrates how to use Remote Settings and DB APIs. The sample allowsyou to configure remote settings in the management console (BlackBerryUEM or standalone Good Control) for this app. The app receives theresponses and stores them in the secure DB. Any changes to the settings areautomatically synchronized and stored.

RSS reader Demonstrates how to use the BlackBerry Dynamics Secure CommunicationAPIs to access resources behind the enterprise firewall.

Greetings server Demonstrates how to write a server that illustrates the BlackBerryDynamics Inter-container Communications (ICC) API. The ICC system is ameans of exchanging data securely between two BlackBerry Dynamics appsrunning on the same device. One app is the server (or "provider") and the otheris the client (or "consumer").

For background on the ICC, see Shared Services Framework.

Greetings client Demonstrates how to write a client that illustrates the BlackBerryDynamics Inter-container Communications (ICC) API. The ICC system is ameans of exchanging data securely between two BlackBerry Dynamics appsrunning on the same device.

For background on the ICC, see Shared Services Framework.

Secure store Demonstrates how to use the BlackBerry Dynamics SDK to create, manage,and access files stored in an app’s secure container. Both the file names andfile contents are encrypted, stored on the device, and can only be accessedwhen the BlackBerry Dynamics app is unlocked.

 | Sample apps | 25

Testing and troubleshootingThis section provides guidance for testing and troubleshooting issues with your BlackBerry Dynamics apps.

Testing with Microsoft Visual StudioYou can use the tools that are available in Microsoft Visual Studio to test and debug your BlackBerryDynamics app.

Implementing automated testing for BlackBerry Dynamics XamarinappsThe BlackBerry Dynamics SDK for Xamarin includes the Common.UITests library to support automated testing.The library is delivered as a .NET solution with the following projects:

• Android.UITests• iOS.UITests• Common.UITests• XamarinForms.UITests

The Common.UITests library includes helper functions for configuring and running tests for Xamarin apps, as wellas classes and helper functions for app provisioning. The library uses the following components:

• Xamarin.UITest• NUnit• Json.NET• Unity

Note that Common.UITests uses the Page Object pattern. You can make your own changes to theCommon.UITests library as necessary.

Automated testing with the BlackBerry Dynamics Xamarin sample appsEach sample app has a corresponding project that includes code for executing an app provisioning test. Theseprojects integrate the Common.UITests library. Note the following details about the Common.UITests integration:

Item  Description

Build target for testing See Prerequisites: Executing automated tests for Android Xamarinapps or Prerequisites: Executing automated tests for iOS Xamarin apps.

Code for Xamarin.UITests The test code, based on the Xamarin.UITests framework, is located inUITests/<platform>.UITests/<AppName>.UITests.

Use of Common.UITests forinteraction

The test code uses helper classes and methods for configuration andprovisioning. For example, the code calls the ProvisionApp method of thestatic Provisioning class, which executes the entire provisioning process.

 | Testing and troubleshooting | 26

Preparing for automated testingAs part of your automated testing, you must activate a new installation of your BlackBerry Dynamics Xamarinapp. This requires a user identifier (typically an email address), an access key, and a password. Common.UITestscan read activation credentials from a file stored in the Resources folder of the Common.UITests project. Forinstructions for configuring the properties in the file, see Execute an automated test for an Android Xamarinapp or Execute an automated test for an iOS Xamarin app.

Please note the following:

• Automated testing works in Enterprise Simulation mode, but has the same restrictions (for example, the appcannot connect to any back-end servers).

• Every BlackBerry Dynamics Xamarin app needs to be initialized to complete activation. The ProvisionAppmethod has been provided to initialize the app.

• Currently, simple authentication is not supported for the automated tests.• For the automated tests you must use a test device or simulator that does not already have a BlackBerry

Dynamics app installed and provisioned. Enterprise Simulation mode does not have this restriction.• There is currently a known issue with iOS simulators where automated tests can fail because the keyboard

occasionally disappears.

Executing automated tests for Android Xamarin appsYou can run the automated tests from Visual Studio for Mac IDE. Running the tests on Windows is not supported.

Prerequisites: Executing automated tests for Android Xamarin apps

• If you are running the tests on a device, enable developer mode.• You need the app .apk file with a signing key. If you want to run the automated tests on an emulator, you must

add the required ABIs when you build the .apk file.• To ensure that the app is granted the required permissions, UITest must install the app, not the IDE. Use

ApkFile() instead of PreferIdeSettings() to force UITest to install the app. For more information, see thisXamarin forum post.

• In the BlackBerry Dynamics policy that is assigned to the test user:

• Set the security timeout to 1 hour• Set the minimum password length to 4 characters• Remove all authentication delegation settings

• In the UEM management console, add the test app to the user's list of allowed apps so that it can beprovisioned.

Execute an automated test for an Android Xamarin app

Before you begin: Follow the Prerequisites: Executing automated tests for Android Xamarin apps.

1. In Visual Studio, open Android.UITests.2. Configure the following properties for the data provider class. If you use the default FileDataProvider class,

configure the properties in Common.UITests/Resources/data.json. If you use the SimpleDataProvider class,configure the properties in Common.UITests/DataServices/BaseSimpleDataProvider.cs.You can change the data provider class in the IDataProvider interface in Common.Android.UITests/Container/ContainerBootstrapper.cs.

Property Value

BinaryPath This is the path of the .apk file.

 | Testing and troubleshooting | 27

Property Value

DeviceIdentifier This is the device identifier.

To get the device identifier, run the following command in the terminal whilethe device is connected or the emulator is open:

$ adb devices

DeviceEcid This property applies only to iOS devices. For Android, specify an emptystring.

AdbPath This is the path of the Android Debug Bridge (ADB) tool.

To get the path, run the following command in the terminal:

$ which adb

Email This is the test user’s email address.

AccessKey This is the user’s 17 character access key, in the format "xxxxx xxxxx xxxxx"or "xxxxx-xxxxx-xxxxx".

You can generate an access key for the user using the UEM managementconsole or the BlackBerry Web Services APIs.

NocAddress This is the address of the BlackBerry Dynamics NOC. For example,“stage11” for the staging NOC and “prod1” for the production NOC.

Password This is the user’s password. The password must meet the passwordrequirements configured in the user’s BlackBerry Dynamics policy.

ConfirmPassword This is the user’s password. The password must meet the passwordrequirements configured in the user’s BlackBerry Dynamics policy.

Example

{ "BinaryPath": "/userDownloads/com.good.gd.example.xf.blankapp.apk", "DeviceIdentifier": "123456a1a12ab1a1", "DeviceEcid": "", //For iOS only "AdbPath": "/user/Library/Android/sdk/platform-tools/adb", "Email": "user@acme.com", "AccessKey": "01234 56789 01234", "NocAddress": "stage11", "Password": "abcd", "ConfirmPassword": "abcd"}

3. Configure the startup project for the test that you want to run.4. Connect the Android device or open the Android emulator with the device identifier that you specified in step 2.5. Run the test.

 | Testing and troubleshooting | 28

Troubleshooting: Executing automated tests for Android Xamarin apps

Issue Possible solution

I get the following error when I try to getdevice identifiers: “error: could not install*smartsocket* listener: Address already inuse”.

Close Visual Studio and run the $ adb devices commandagain.

app.EnterText does not work as expectedon a test device using Android API 29.

See this bug report.

Executing automated tests for iOS Xamarin appsYou can run the automated tests from Visual Studio for Mac IDE. Running the tests on Windows is not supported.

Prerequisites: Executing automated tests for iOS Xamarin apps

• If you are running the tests on a device, enable developer mode.• You need the app binary file.• In the BlackBerry Dynamics policy that is assigned to the test user:

• Set the security timeout to 1 hour• Set the minimum password length to 4 characters• Remove all authentication delegation settings

• In the UEM management console, add the test app to the user's list of allowed apps so that it can beprovisioned.

• Install the Apple Configurator command-line tool. If you do not want to use this tool, you can usean iOS simulator instead of an iOS device, or you can implement your own installation mechanism that uses adifferent BuildConfiguration.

Execute an automated test for an iOS Xamarin app

Before you begin: Follow the Prerequisites: Executing automated tests for iOS Xamarin apps.

1. In Visual Studio, open iOS.UITests.2. Configure the following properties for the data provider class. If you use the default FileDataProvider class,

configure the properties in Common.UITests/Resources/data.json. If you use the SimpleDataProvider class,configure the properties in Common.UITests/DataServices/BaseSimpleDataProvider.cs.You can change the data provider class in the IDataProvider interface in Common.iOS.UITests/Container/ContainerBootstrapper.cs.

Property Value

BinaryPath This is the path of the .ipa or .app file.

 | Testing and troubleshooting | 29

Property Value

DeviceIdentifier This is the device identifier.

To get the identifier (UDID) for an iOS device, run the followingcommand in the terminal:

$ cfgutil list-devices

To get the simulator device identifier (UUID), run the followingcommand in the terminal:

$ xcrun simctl list

DeviceEcid To get the ECID for an iOS device, run the following command in theterminal:

$ cfgutil list-devices

If you are using an iOS simulator, specify an empty string.

AdbPath This property applies only to Android devices. For iOS, specify anempty string.

Email This is the test user’s email address.

AccessKey The user’s 17 character access key, in the format "xxxxx xxxxx xxxxx"or "xxxxx-xxxxx-xxxxx".

You can generate an access key for the user usingthe UEM management console or the BlackBerry Web Services APIs.

NocAddress This is the address of the BlackBerry Dynamics NOC. For example,“stage11” for the staging NOC and “prod1” for the production NOC.

Password This is the user’s password. The password must meet the passwordrequirements configured in the user’s BlackBerry Dynamics policy.

ConfirmPassword This is the user’s password. The password must meet the passwordrequirements configured in the user’s BlackBerry Dynamics policy.

Example for an iOS app

{ "BinaryPath": "/userDownloads/com.good.gd.example.xf.blankapp.ipa", "DeviceIdentifier": "12a12a12a123abcd12a123456ab1a12ab1ab123a", "DeviceEcid": "0x12345678A123A", "AdbPath": "" //For Android only "Email": "user@acme.com", "AccessKey": "01234 56789 01234", "NocAddress": "stage11", "Password": "abcd", "ConfirmPassword": "abcd"}

 | Testing and troubleshooting | 30

Example for an iOS simulator

{ "BinaryPath": "/userDownloads/com.good.gd.example.xf.blankapp.app", "DeviceIdentifier": "AB123A12-1234-1ABC-ABCD-12A12A12A1AB", "DeviceEcid": "", //For iOS only, not required for iOS simulator "AdbPath": "" //For Android only "Email": "user@acme.com", "AccessKey": "01234-56789-01234", "NocAddress": "stage11", "Password": "abcd", "ConfirmPassword": "abcd"}

3. Configure the startup project for the test that you want to run.4. Connect the iOS device or open the simulator with the device identifier that you specified in step 2.5. If you are using an iOS simulator, turn off the hardware keyboard.6. Run the test.

Troubleshooting: Executing automated tests for iOS Xamarin apps

Issue Possible solution

I get an “Address already in use” deviceerror.

This error may occur if you run the test on an iOS device whilean iOS simulator is open. Close all simulators.

For more information, see this Xamarin forum post.

The simulator UI isn’t visible when I runthe test.

Run the following command in the terminal:

$ open /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/

Touch screen coordinates are incorrect. UITest must run an app in the device’s native resolution. Ifyou encounter this issue, run the test on the previous deviceor simulator version. For example, if you run into this issuewith iPhone 8, run the test for iPhone 7.

Alternatively, use only the GreetingsServer, GreetingsClient, orRssReader apps for testing.

For more information, see this Xamarin forum post.

Executing automated tests for Xamarin.Forms appsYou can run the automated tests from Visual Studio for Mac IDE. Running the tests on Windows is not supported.

Prerequisites: Executing automated tests for Xamarin.Forms apps

• Depending on the platforms that you are using, follow the Prerequisites: Executing automated testsfor Android Xamarin apps and the Prerequisites: Executing automated tests for iOS Xamarin apps.

• Open and build the archive for the proper Xamarin.Forms app (for example, SampleAppSuite.Droid orSampleAppSuite.iOS).

 | Testing and troubleshooting | 31

Execute an automated test for a Xamarin.Forms app

Follow the Prerequisites: Executing automated tests for Xamarin.Forms apps.

1. In Visual Studio, open XamarinForms.UITests.2. Open the test that you want to execute (for example, SampleAppSuite.UITests/Tests.cs).3. Comment out the TestFixture attribute for any platform that you don’t want to run the test on.4. Depending on the platforms that you are using, follow step 2 in Execute an automated test for

an Android Xamarin app or Execute an automated test for an iOS Xamarin app.

 | Testing and troubleshooting | 32

Deploying your BlackBerry Dynamics appBefore you deploy your BlackBerry Dynamics app to your organization’s production environment, you shouldtest the app and the deployment process in a BlackBerry UEM or standalone Good Control environment that isreserved for development testing and evaluation. Coordinate with your organization’s administrator to get accessto a dedicated test environment.

BlackBerry Dynamics apps are fully supported for BlackBerry UEM and for standalone Good Control. BlackBerryUEM is the recommended enterprise management solution to implement and use going forward, because itprovides advanced app and user management features, advanced connectivity and networking options, expandedcompliance and integrity checking, and the most recent BlackBerry Web Services REST APIs that your apps canleverage.

See the following resources for more information about distributing and managing your app in a BlackBerryUEM environment: 

Task Resource 

Add your app to BlackBerry UEM and distribute it tousers

See the following topics in the BlackBerry UEMAdministration Guide:

• Apps• Add an internal BlackBerry Dynamics app

entitlement • Managing BlackBerry Dynamics apps 

Configure BlackBerry Dynamics profiles that impactapp functionality 

See the following topics in the BlackBerry UEMAdministration Guide:

• Controlling BlackBerry Dynamics on users devices• BlackBerry Dynamics profile settings• BlackBerry Dynamics connectivity profile settings• Assigning profiles 

Collect activity and compliance violation informationfor BlackBerry Dynamics apps 

 See the following topic in the BlackBerry UEMAdministration Guide:

• Activity and compliance violation reports forBlackBerry Dynamics apps

For more information about testing and distributing BlackBerry Dynamics apps using standalone Good Control,see Developer Bootstrap: Good Control Essentials and the Good Control documentation.

 | Deploying your BlackBerry Dynamics app | 33

Deploying certificates to BlackBerry Dynamics appsYou can use any of the following options to deploy certificates to BlackBerry Dynamics apps. Each methodrequires configuration in the BlackBerry UEM or standalone Good Control management console. Coordinate withyour organization's administrator to select and configure the desired option.

Option For more information

Personal Information Exchangefiles

See Using Personal Information Exchange files in this section.

CA certificate profile See Sending CA certificates to devices and apps in the UEMAdministration Guide.

User credential profile See Sending client certificates to devices and apps using user credentialprofiles in the UEM Administration Guide.

SCEP profile See Sending client certificates to devices and apps using SCEP inthe UEM Administration Guide.

Shared certificate profile See Sending the same client certificate to multiple devices in the UEMAdministration Guide.

After certificates are distributed to a user's device, those certificates are shared and used by all of the BlackBerryDynamics apps on the device. No additional programming is required by the app developer to support clientcertificates.

The management server and BlackBerry Dynamics apps also support the use of Kerberos for serviceauthentication. For more information, see Using Kerberos in this section.

The SDK also provides a Crypto C language programming interface that allows an app to retrieve public keycertificates that are stored in the BlackBerry Dynamics credentials store and use those certificates for signing andverification of messages and documents such as PDFs. Note that BlackBerry Infrastructure certificates cannot beretrieved from the store and that the private key will remain inaccessible. For more information, see the Crypto CProgramming Interface appendix (Android/iOS) in the API reference.

Using Personal Information Exchange filesAn organization can deploy corporate services that require two-way SSL/TLS authentication for users. A useris issued a password-protected Personal Information Exchange file (PKCS12 format, .p12 or .pfx) containingan SSL/TLS client certificate and a private key. This file can be provided to BlackBerry Dynamics apps to grantaccess to secure corporate services.

The BlackBerry Dynamics SDK supports the use of Personal Information Exchange files toauthenticate BlackBerry Dynamics apps and to access secure services. All of the required operations to supportclient certificates are carried out by the BlackBerry Dynamics Runtime, with no additional programming required.The app can use client certificates if:

• The app uses the BlackBerry Dynamics Secure Communication Networking APIs.• The device user’s UEM or standalone Good Control account is configured to support certificates.• The certificates satisfy the certificate requirements. 

 | Deploying certificates to BlackBerry Dynamics apps | 34

After a user activates a BlackBerry Dynamics app, the app receives the Personal Information Exchange files. Foreach file, the user is prompted to provide the issued password so that the files and identification material can beinstalled. When this process is complete, the app can access the server resources that require two-way SSL/TLSauthentication.

If more than one Personal Information Exchange file is required per user, the BlackBerry DynamicsRuntime selects the appropriate certificate using the following criteria:

1. Only client certificates that are suitable for SSL/TLS client authentication are eligible to send to the server.Certificates must have no Key Usage or Extended Key Usage, or Key Usage that contains “Digital Signature"or "Key Agreement”, or Extended Key Usage that contains "TLS Web Client Authentication”. Key Usages andExtended Key Usages must not contradict allowances for SSL/TLS client authentication.

2. If the server advertises the client certificate authority in the SSL/TLS handshake, only client certificates thathave been issued by that authority are considered.

3. Expired certificates and certificates that are not yet valid cannot be selected.4. If more than one certificate satisfies the above criteria, the BlackBerry Dynamics Runtime selects the most

recently issued certificate. 

Configuring support for client certificatesCertificate support is configured in the BlackBerry UEM or standalone Good Control management console bythe administrator. Contact your organization’s administrator to configure certificate support for BlackBerryDynamics apps.

For more information about configuring certificate support in BlackBerry UEM, see the following:

• Manage settings for a BlackBerry Dynamics app in the UEM Administration Guide• Sending certificates to devices using profiles in the UEM Administration Guide • Connect BlackBerry UEM to a BlackBerry Dynamics PKI Connector in the UEM Administration Guide

For more information about configuring certificate support in standalone Good Control, see the Good Control andGood Proxy Admin Help.

Certificate requirements• Client certificates must be in PKCS12 format, with the Certificate Authority (CA), public key, and private key in

the same file.• The PKCS12 file must have a .p12 or .pfx extension• The PKCS12 file must be password-protected• The source of the certificate can be your own internal CA, a well-known public CA, or an online tool such

as OpenSSL or the Java keytool. You can use the following keytool example to generate a certificate,substituting your own values as required: 

keytool -genkeypair -alias good123 -keystore good123.pfx -storepass good123 -validity 365 -keyalg RSA -keysize 2048 -storetype pkcs12

• If the organization’s security policy uses FIPS standards, Personal Information Exchange files must beencrypted with FIPS-strength ciphers. If Personal Information Exchange files use a weak cipher, which iscommon for third-party applications when exporting identity material, you can use a tool like OpenSSL to re-encrypt the files with a FIPS-strength cipher. See the following example:

openssl pkcs12 -in weak.p12 -nodes -out decrypted.pem <enter password> openssl pkcs12 -export -in decrypted.pem -keypbe AES-128-CBC -certpbe AES-128-CBC -out strong.p12 <enter password>

 | Deploying certificates to BlackBerry Dynamics apps | 35

rm decrypted.pem

Using KerberosBlackBerry Dynamics apps support both Kerberos PKINIT with PKI certificates and Kerberos ConstrainedDelegation. Kerberos PKINIT and Kerberos Constrained Delegation are distinct implementations of Kerberos. Youcan support one or the other for BlackBerry Dynamics apps, but not both.

With Kerberos PKINIT, authentication occurs directly between the BlackBerry Dynamics app and the Windows KeyDistribution Center (KDC). User authentication is based on certificates that are issued by MicrosoftActive Directory Certificate Services. No additional programming is required by the app developer touse Kerberos PKINIT.

With Kerberos Constrained Delegation, authentication is based on a trust relationship between the managementserver (BlackBerry UEM or standalone Good Control) and a KDC. The management server communicates with theservice on behalf of the app.

Note: The BlackBerry Dynamics GDHTTPRequest method does not support Kerberos ConstrainedDelegation (KCD). If you plan to develop iOS apps for use with KCD, you can use the NSURLSystem providedby Apple instead.

For more information about how to configure the desired Kerberos implementation in UEM, includingrequirements and prerequisites, see Configuring Kerberos for BlackBerry Dynamics apps in the UEM AdministrationGuide.

For more information about configuring the desired Kerberos implementation in Good Control, see the GoodControl and Good Proxy Admin Help and Kerberos Constrained Delegation with Good Control. 

 | Deploying certificates to BlackBerry Dynamics apps | 36

Legal notice ©2020 BlackBerry Limited. Trademarks, including but not limited to BLACKBERRY, BBM, BES, EMBLEM Design,ATHOC, CYLANCE and SECUSMART are the trademarks or registered trademarks of BlackBerry Limited, itssubsidiaries and/or affiliates, used under license, and the exclusive rights to such trademarks are expresslyreserved. All other trademarks are the property of their respective owners. 

 This documentation including all documentation incorporated by reference herein such as documentationprovided or made available on the BlackBerry website provided or made accessible "AS IS" and "AS AVAILABLE"and without condition, endorsement, guarantee, representation, or warranty of any kind by BlackBerry Limited andits affiliated companies ("BlackBerry") and BlackBerry assumes no responsibility for any typographical, technical,or other inaccuracies, errors, or omissions in this documentation. In order to protect BlackBerry proprietary andconfidential information and/or trade secrets, this documentation may describe some aspects of BlackBerrytechnology in generalized terms. BlackBerry reserves the right to periodically change information that is containedin this documentation; however, BlackBerry makes no commitment to provide any such changes, updates,enhancements, or other additions to this documentation to you in a timely manner or at all. 

This documentation might contain references to third-party sources of information, hardware or software,products or services including components and content such as content protected by copyright and/or third-party websites (collectively the "Third Party Products and Services"). BlackBerry does not control, and is notresponsible for, any Third Party Products and Services including, without limitation the content, accuracy,copyright compliance, compatibility, performance, trustworthiness, legality, decency, links, or any other aspectof Third Party Products and Services. The inclusion of a reference to Third Party Products and Services in thisdocumentation does not imply endorsement by BlackBerry of the Third Party Products and Services or the thirdparty in any way.

EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR JURISDICTION, ALLCONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, OR WARRANTIES OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY CONDITIONS, ENDORSEMENTS, GUARANTEES,REPRESENTATIONS OR WARRANTIES OF DURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE,MERCHANTABILITY, MERCHANTABLE QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, ORARISING FROM A STATUTE OR CUSTOM OR A COURSE OF DEALING OR USAGE OF TRADE, OR RELATED TO THEDOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE,SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN, ARE HEREBY EXCLUDED.YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR PROVINCE. SOME JURISDICTIONS MAYNOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO THE EXTENTPERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE DOCUMENTATION TOTHE EXTENT THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, ARE HEREBY LIMITED TONINETY (90) DAYS FROM THE DATE YOU FIRST ACQUIRED THE DOCUMENTATION OR THE ITEM THAT IS THESUBJECT OF THE CLAIM.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALLBLACKBERRY BE LIABLE FOR ANY TYPE OF DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE,OR PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRDPARTY PRODUCTS AND SERVICES REFERENCED HEREIN INCLUDING WITHOUT LIMITATION ANY OF THEFOLLOWING DAMAGES: DIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE,OR AGGRAVATED DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES, FAILURE TO REALIZE ANYEXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF BUSINESSOPPORTUNITY, OR CORRUPTION OR LOSS OF DATA, FAILURES TO TRANSMIT OR RECEIVE ANY DATA,PROBLEMS ASSOCIATED WITH ANY APPLICATIONS USED IN CONJUNCTION WITH BLACKBERRY PRODUCTS ORSERVICES, DOWNTIME COSTS, LOSS OF THE USE OF BLACKBERRY PRODUCTS OR SERVICES OR ANY PORTIONTHEREOF OR OF ANY AIRTIME SERVICES, COST OF SUBSTITUTE GOODS, COSTS OF COVER, FACILITIES ORSERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARY LOSSES, WHETHER OR NOT SUCH DAMAGES

 | Legal notice | 37

WERE FORESEEN OR UNFORESEEN, AND EVEN IF BLACKBERRY HAS BEEN ADVISED OF THE POSSIBILITY OFSUCH DAMAGES.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, BLACKBERRY SHALLHAVE NO OTHER OBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TOYOU INCLUDING ANY LIABILITY FOR NEGLIGENCE OR STRICT LIABILITY.

THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATUREOF THE CAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OFCONTRACT, NEGLIGENCE, TORT, STRICT LIABILITY OR ANY OTHER LEGAL THEORY AND SHALL SURVIVE AFUNDAMENTAL BREACH OR BREACHES OR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENTOR OF ANY REMEDY CONTAINED HEREIN; AND (B) TO BLACKBERRY AND ITS AFFILIATED COMPANIES, THEIRSUCCESSORS, ASSIGNS, AGENTS, SUPPLIERS (INCLUDING AIRTIME SERVICE PROVIDERS), AUTHORIZEDBLACKBERRY DISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE PROVIDERS) AND THEIR RESPECTIVEDIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS.

IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL ANY DIRECTOR,EMPLOYEE, AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR OF BLACKBERRY OR ANYAFFILIATES OF BLACKBERRY HAVE ANY LIABILITY ARISING FROM OR RELATED TO THE DOCUMENTATION.

Prior to subscribing for, installing, or using any Third Party Products and Services, it is your responsibility toensure that your airtime service provider has agreed to support all of their features. Some airtime serviceproviders might not offer Internet browsing functionality with a subscription to the BlackBerry® Internet Service.Check with your service provider for availability, roaming arrangements, service plans and features. Installationor use of Third Party Products and Services with BlackBerry's products and services may require one or morepatent, trademark, copyright, or other licenses in order to avoid infringement or violation of third party rights. Youare solely responsible for determining whether to use Third Party Products and Services and if any third partylicenses are required to do so. If required you are responsible for acquiring them. You should not install or useThird Party Products and Services until all necessary licenses have been acquired. Any Third Party Products andServices that are provided with BlackBerry's products and services are provided as a convenience to you and areprovided "AS IS" with no express or implied conditions, endorsements, guarantees, representations, or warrantiesof any kind by BlackBerry and BlackBerry assumes no liability whatsoever, in relation thereto. Your use of ThirdParty Products and Services shall be governed by and subject to you agreeing to the terms of separate licensesand other agreements applicable thereto with third parties, except to the extent expressly covered by a license orother agreement with BlackBerry.

The terms of use of any BlackBerry product or service are set out in a separate license or other agreement withBlackBerry applicable thereto. NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESSWRITTEN AGREEMENTS OR WARRANTIES PROVIDED BY BLACKBERRY FOR PORTIONS OF ANY BLACKBERRYPRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION.

BlackBerry Enterprise Software incorporates certain third-party software. The license and copyright informationassociated with this software is available at http://worldwide.blackberry.com/legal/thirdpartysoftware.jsp.

BlackBerry Limited2200 University Avenue EastWaterloo, OntarioCanada N2K 0A7

BlackBerry UK LimitedGround Floor, The Pearce Building, West Street,Maidenhead, Berkshire SL6 1RLUnited Kingdom

Published in Canada

 | Legal notice | 38