Migration and Precedence

Android Migration Steps

1. Add Configuration File: Place the moengage.xml file in src/main/res/values/moengage.xml.
2. Update Application Class: Remove manual MoEngage.Builder logic and replace it with initializeDefaultInstance.

Java

import com.moengage.react.MoEInitializer;
MoEInitializer.INSTANCE.initializeDefaultInstance(this);

Kotlin

import com.moengage.react.MoEInitializer
MoEInitializer.initializeDefaultInstance(application)

iOS Migration Steps

1. Update Info.plist: Add WorkspaceId, DataCenter, etc., directly to your Info.plist file.
2. Update AppDelegate: Remove manual MoEngageSDKConfig logic and call initializeDefaultInstance.

Objective-C

#import <MoEngageSDK/MoEngageSDK.h>
[[MoEngageInitializer sharedInstance] initializeDefaultInstanceWithAdditionalReactConfig:[[MoEngageReactSDKDefaultInitializationConfig alloc] init]];

Swift

import MoEngageSDK
MoEngage.sharedInstance.initializeDefaultInstance()

Precedence Rules

The source of configuration is determined by the initialization function called in your native code:

• Android:
  • File-Based Init: initializeDefaultInstance(context) reads moengage.xml.
  • Code-Based Init: initialize(context, moEngage.Builder) uses the configuration object and ignores XML.
• iOS: Auto-initialization via Info.plist occurs first. Calling the manual initialize method with a configuration object later will update the current instance.