Get the APP 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 the worker thread.
// this is the instance of the application class and "XXXXXXXXXXX" is the APP ID from the dashboard. MoEngage.Builder moEngage = new MoEngage.Builder(this, "XXXXXXXXXXX"); MoEInitializer.INSTANCE.initializeDefaultInstance(getApplicationContext(), moEngage);
In case you are facing issues with the import add the below import statement to your java file.
import com.moengage.core.MoEngage; import com.moengage.react.MoEInitializer;
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.
In case your app wants to redirect data to a specific zone due to any data regulation policy please configure the zone in the MoEngage initializer object. Use the setDataCenter() in the MoEngage.Builder to specify the data center.
Refer to the Data Center documentation for more information.