Using the iOS Trust SDK
This guide is written for developers who want to use the Trust SDK to add local (on-device) Onboarding capabilities to an iOS application.
The sample application for the Trust SDK is recommended as a starting point for learning how to integrate the SDK with your own code.
The developer needs a thorough knowledge of the Swift and/or Objective-C programming language on the iOS platform. It is also recommended that the developer has some understanding of TrustX technology.
The minimum supported iOS version is 14.3.
Add the Trust SDK to your Project
Copy the following xcframework files to your project folder and reference it in project general settings, frameworks and libraries
DaonTrustSDK.xcframeworkDaonNFCSDK.xcframeworkImport the Library
import DaonTrustSDKInitializing the Trust SDK
- The SDK provides simple and straightforward initialization mechanism:
let sdk = TrustSDK(withViewController: self, delegate: self)- Daon Trust SDK offers setting a DaonOptions object for customization purposes. You can set your own initialization timeout as well as the URL of the environment that you want to use:
let options = DaonOptions()options.serverUrl = "https://www.example.com"options.initializationTimeout = 15If you do not set the DaonOptions object, default values will be used. Initialization timeout default value is 10. By not setting the custom environment URL, you are requesting of the Daon Trust SDK to launch a QR code scanning feature which expects the QR code that carries the URL of your environment as a value.
- Finally, you can start the Onboarding process by calling 'start()' function of the TrustSDK:
sdk.start(withDaonOptions: options)Obtaining and Parsing Events from the Trust SDK
In utilizing DaonEventDelegate, three delegate methods need
to be called. Events that are returned are represented through the
DaonEvent object instances that are carrying feedback information about
the Onboarding process status and errors. The event delegate methods
required are listed below.
func didReceive(successResponse daonEvent: DaonEvent) {...}func didReceive(failedResponse daonEvent: DaonEvent) {...}func didReceive(infoResponse daonEvent: DaonEvent) {...}DaonEvent fields:
DaonEvent fields are derived from an event code and description:
- DaonEventCode - A field that contains event code
- String description - A field that contains a description of the event
A list of events, their codes and descriptions that are supported and provided by the Daon Trust SDK can be found below:
| Event Name | Code | Description |
|---|---|---|
webSessionCompleted | 100403 | Web session for onboarding process completed successfully. |
qrScanInvalidQRCode | 200103 | Scanned QR code is not valid. |
qrScanInterrupted | 200104 | QR code scanning interrupted. Please try again. |
webAppTerminated | 200402 | Web application process terminated. This can occur when the end-user presses the back button to navigate to a previous screen when they are on the first web screen of the Process Instance. |
webAppTimeout | 200403 | Web application process has timed out. |
cameraPermissionDenied | 200501 | Camera permission denied. |
noInternetConnection | 200502 | Internet connection not available. |
notSupportediOS | 200503 | Returned when current iOS version not supported. |
versionNotCompatible | 200505 | Returned when DaonTrust SDK client version not compatible with server version. |
urlNotWhitelisted | 200508 | Provided URL is not whitelisted. |
webLoadingTimeout | 200509 | Web page failed to load in given time frame. |
- DaonEventCode structure breakdown:
- The first pair of digits represents event status. Event status can be: Success (10), Fail (20), Info (30).
- The second pair of digits represents section of the event. Event sections can be: QR (01), MRZ (02), NFC (03), Web (04), Other (05).
- The third pair of digits represents ordinal code number for that section.