Android SDK Initialization 5.2.0


Initialize the SDK on the main thread inside onCreate() and not create a worker thread and initialize the SDK on that thread.
import com.moengage.flutter.MoEInitializer
import com.moengage.core.MoEngage
import com.moengage.core.DataCenter
// `this` is the instance of the application class and "YOUR_APP_ID" is the APP ID from the dashboard.
val moEngage: MoEngage.Builder = MoEngage.Builder(this,"YOUR_APP_ID")
MoEInitializer.initialiseDefaultInstance(context = this, builder = moengage);

Following details of the different data centers you need to set based on the dashboard hosts

Data Center Dashboard host






For more information about the detailed list of possible configurations, refer to the API reference.



All the configurations are added to the builder before initialization. If you are calling initialize at multiple places, ensure that all the required flags and configurations are set each time you initialize to maintain consistency in behavior.

Exclude MoEngage Storage File from Auto-Backup

This is a mandatory integration step and is very essential to prevent your data from getting corrupted. Android's auto back-up service periodically backs up Shared Preference files, Database files, etc, more details here. This backup results in MoEngage SDK's identifiers being backed up and restored after re-install.This restoration of the identifier results in your data being corrupted and users not being reachable via push notifications.

To ensure data is not corrupted after a backup is restored, opt out of MoEngage SDK's storage files. Refer to Exclude MoEngage Storage File from the Auto-Backup section of the documentation to learn more about which files to exclude.



Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?