Android

Initialize the MoEngage SDK in your Android Application class for React Native integration.

SDK Initialization

Get the Workspace ID from the Settings Page _Dashboard —> Settings —> App —> Genera_l 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 the worker thread.

Kotlin

import com.moengage.core.DataCenter
import com.moengage.core.MoEngage
import com.moengage.react.MoEInitializer

val moEngage = MoEngage.Builder(this, "YOUR_Workspace_ID", DataCenter.DATA_CENTER_X)
//replace X with your data center number
MoEInitializer.initializeDefaultInstance(applicationContext, moEngage)

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

Data Center	Dashboard host
DataCenter.DATA_CENTER_1	dashboard-01.moengage.com
DataCenter.DATA_CENTER_2	dashboard-02.moengage.com
DataCenter.DATA_CENTER_3	dashboard-03.moengage.com
DataCenter.DATA_CENTER_4	dashboard-04.moengage.com
DataCenter.DATA_CENTER_5	dashboard-05.moengage.com
DataCenter.DATA_CENTER_6	dashboard-06.moengage.com

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.