Quick Start
Getting Started / iOS
Overall Code
A quick start snippet will look something like this in your app's willFinishLaunchWithOptions:
import DolphinMoveSDK
#if canImport(DolphinMoveSDKHealth)
import DolphinMoveSDKHealth
#endif
func application(_ application: UIApplication, willFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil) -> Bool {
#if canImport(DolphinMoveSDKHealth)
sdk.enable(healthKit: MoveSDKHealth.shared)
#endif
MoveSDK.shared.setSDKStateListener { sdkState in
switch state {
case .uninitialized:
print("/* SDK uninitialized*/")
break
case .ready:
print("/* SDK initialised and ready to start the service*/")
break
case .running:
print("/* SDK Started Detection*/")
break
}
}
MoveSDK.shared.setAuthStateUpdateListener { authState in ... }
MoveSDK.shared.setTripStateListener { tripState in ... }
MoveSDK.shared.setServiceFailureListener { failures in ... }
MoveSDK.shared.setServiceWarningListener { warnings in ... }
MoveSDK.shared.initialize(launchOptions: launchOptions)
}This snippet assumes that the required configurations and permissions are already setup to work. Check the permissions handling section for more details.
SDK Authorization and Setup
Users will need to be authenticated. This authentication will persist until shutdown is called. It will persist over the termination of the app. The configuration to enable functionality is passed here. startAutomaticDetection will start the services. This too will persist and services will automatically start when launching the app from the background.
Authentication Invalidation
The host app is expected to monitor MoveAuthState updates viaauthStateChangeListener(iOS) API and handle those changes accordingly.
Check Authentication updates and expiry for more details about authentication expiry and renewal.
An auth state listener must be implemented to handle user invalidation, which can happen due to a user being blocked or having multiple conflicting installations with the same user.
SDK State
The host app is expected to set its SDKStateListener before initializing the SDK to intercept the MoveSDKState changes.
The provided block could then start the SDK when MoveSDKState is ready or handle errors if occurred. The provided block could look something like this:
SDK Initialization
TheinitializationAPI must be executed beforedidFinishLaunchingWithOptionsreturns. We recommend calling it inwillFinishLaunchingWithOptions.
Exceptions might apply, where the SDK is not initialized on app launch. First initialization is a good example, where the app would only initialize the SDK after onboarding the user and requesting permissions.
Check Initialization Timing for more details about the importance of adequately initializing the SDK.
Warnings and Errors
When services are not running properly because they are missing permissions or are not authorized on the backend, warnings or errors will be reported in the corresponding listeners.
WORKING SAMPLE CODE
Last updated