This document refers to deprecated parts of the platform and has been left intact to help customers with legacy integrations. In order to access the latest platform features and documentation, please go to https://docs.sentiance.com.
You can use the SDK calls in your App code in both Swift and Objective-C. If your app is written in Swift, You will need to add a bridging header (if you don't have one already in your project).
Import SENTSDK public header in your bridging header file to access the SDK:
@import SENTSDK;
You will also need to setup Location Authorization Permission before initializing the SDK. The Sentiance SDK does not handle location authorizations but needs it to function. Add the necessary code in your app following the for Location Services Authorizations before initializing the SDK.
In the didFinishLaunchingWithOptions method of your AppDelegate, create a object with your Sentiance app ID and secret.
If you don't have an appID and secret key yet, read .
In the above example, we hard-code the the appID and secret key for testing purposes. However, this is not secure and can lead to leaked credentials. In your own app, load these credentials from a secure source such a remote server, and store them securely on the device.
SENTConfig accepts a userLinker which is responsible for handling . The linker is invoked by the SDK when creating a Sentiance user (during the first initialization) to give you a chance to link your app's user to the Sentiance user. If linking succeeds, this linker does not get invoked during subsequent SDK intializations, unless .
MetaUserLinker userLinker = ^(NSString *installId, void (^linkSuccess)(void), void (^linkFailed)(void)) {
// Supply the 'installId' to your server, which should then initiate
// a user linking request with the Sentiance backend.
[self requestLinking:installId completion:^(BOOL success) {
if (success) {
linkSuccess(); // Call if linking succeeds
} else {
linkFailed(); // Call if linking fails
}
}];
};
Until the SDK is properly initialized, none of the methods in the SDK will work, with the exception of sharedInstance, initWithConfig and getInitState.
In the project's AppDelegate file,
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
// Setup Config.
let config = SENTConfig(appId: self.appId, // Add yours.
secret: self.secret, // Add yours.
link: userLinker // If user linking.
launchOptions: launchOptions)
// Initialize SDK.
SENTSDK.sharedInstance().initWith(config,
success: { // Successful Initialization
// Add code to start service.
self.startService()
},
failure: { issue in
print("Failed to Initialize SDK with issue: \(issue)")
})
}
We recommend that SDK startup is done within didFinishLaunchingWithOptions of AppDelegate file to ensure that there are no unintended side effects.
SENTSDK.sharedInstance().start { status in
if let status = status {
switch status.startStatus {
case SENTStartStatus.notStarted:
print("SDK Status: Not started")
case SENTStartStatus.pending:
print("SDK Status: Pending")
case SENTStartStatus.started:
print("SDK Status: Started")
case SENTStartStatus.expired:
print("SDK Status: Expired")
@unknown default:
print("Status unknown")
}
}
}
[[SENTSDK sharedInstance] start:^(SENTSDKStatus *status) {
if ([status startStatus] == SENTStartStatusStarted) {
// SDK started properly.
} else if ([status startStatus] == SENTStartStatusPending) {
// Something prevented the SDK to start properly (check the location permission). Once fixed, the SDK will start automatically.
} else {
// SDK did not start.
}
}];
You can check the status to see whether starting has succeeded correctly or not.
Overall Code
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
// Handle Location permissions before-hand.
// Setup Config.
let config = SENTConfig(appId: "", // Add yours.
secret: "", // Add yours.
link: userLinker // If user linking.
launchOptions: launchOptions)
// Initialize SDK.
SENTSDK.sharedInstance().initWith(config,
success: {
// Start the SDK
SENTSDK.sharedInstance().start { status in
// Handle the start status.
}
},
failure: { issue in
print("Failed to Initialize the SDK due to issue: \(issue)")
})
return true
}
@import SENTSDK;
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
// Creation of SENTConfig here, see previous step
SENTConfig *conf = [[SENTConfig alloc] initWithAppId:@"APPID"
secret:@"SECRET"
link:userLinker
launchOptions:launchOptions];
// Initialize SDK
[[SENTSDK sharedInstance] initWithConfig:conf success:^{
// SDK Start
[[SENTSDK sharedInstance] start:^(SENTSDKStatus *status) {
if ([status startStatus] == SENTStartStatusStarted) {
// SDK started properly.
} else if ([status startStatus] == SENTStartStatusPending) {
// Something prevented the SDK to start properly (check the location permission). Once fixed, the SDK will start automatically.
} else {
// SDK did not start.
}
}];
} failure:^(SENTInitIssue issue) {
}];
return YES;
}
You can learn more about user linking .
This step is optional, but indispensable if you want to be kept up-to-date with changes to the .
In the didFinishLaunchingWithOptions method of your AppDelegate, pass the you created in the previous step to the initWithConfig method of the Sentiance SDK.
Additionally, and blocks must be passed as well, which will inform you when initialization has succeeded or failed.
The call must be executed before didFinishLaunchingWithOptions: returns. Therefore, you must call it synchronously on the main UI thread. If you plan to add a remote flag to control the initialization (e.g. Firebase Remote Config), make sure the check is synchronous (e.g. using a cached flag).
See to understand more about why this is important.
Call the start method from the success block of the method:
