Android SDK Initialization


Get the Workspace ID from the Settings Page Dashboard --> Settings --> App --> General on the MoEngage dashboard and initialize the MoEngage SDK in the Application class's onCreate()



It is recommended that you 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.cordova.MoEInitializer;
import com.moengage.core.MoEngage;

// this is the instance of the application class and "YOUR_Workspace_ID" is the Workspace ID from the dashboard.
MoEngage.Builder moEngage = new MoEngage.Builder(this,"YOUR_Workspace_ID”);
MoEInitializer.initialiseDefaultInstance(this, moEngage);

In case your application does not have an Application class yet navigate to java source code inside the android platform folder and add the Application class file.


Make sure your application class is defined in the AndroidManifest.xml file as well.
Refer to the API reference doc for a detailed list of possible configurations.

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?