FAQ
SDK
Important topics
Data Explorer
4. Initialization
Initialization is a very important step; before initialization, none of the methods on the Sentiance SDK interface will work, with the exception of
getInstance(), init() and getInitState().Create an Application Class
Initialization must be done in the
onCreate() method of your Application class. If you don't already have a custom application class, first create a new class that extends Application.1
import android.app.Application;
2
public class MyApplication extends Application {
3
@Override
4
public void onCreate() {
5
}
6
}
Copied!
Then reference this new class in the application tag of the
AndroidManifest.xml1
<application android:name="com.example.appname.MyApplication">
2
<!-- Activities -->
3
</application>
Copied!
Call the SDK init Method
In the
onCreate() method of your Application class, call init() and pass the SdkConfig you created in the previous step, plus an instance of OnInitCallback to handle the initialization result. MyApplication.java
1
@Override
2
public void onCreate() {
3
// Creation of SdkConfig here, see previous step
4
5
OnInitCallback initCallback = new OnInitCallback() {
6
@Override
7
public void onInitSuccess() {
8
}
9
@Override
10
public void onInitFailure(InitIssue issue, @Nullable Throwable th) {
11
}
12
};
13
14
Sentiance.getInstance(this).init(sdkConfig, initCallback);
15
}
Copied!
Upon successful initialization,
onInitSuccess() will be called. If it fails, onInitFailure() will be called with an appropriate InitIssue.The
init() call must be executed before onCreate() returns. Therefore, you must call it synchronously on the main 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 here to understand more about why this is important. An example app demonstrating this can be found on our Github.
Last modified 3mo ago
Copy link