Initializing MoEngage SDK

First, go to Build Settings of your App Target and ensure that DEBUG Preprocessor Macro is defined in Debug section as shown in the below image, if not present then add the same by entering DEBUG=1 in Debug section:

For Swift Project, In App Target Build Settings make sure -DDEBUG is added to Debug section in the Other Swift Flags as described in the image:

in to your MoEngage account, go to Settings in the left panel of the dashboard. Under General Settings, you will find your Workspace ID. Provide this Workspace ID  along with the Datacenter while initializing the SDK with MoEngageSDKConfig instance . Use initializeDefaultTestInstance(_:) and initializeDefaultLiveInstance(_:) methods as shown below.

import MoEngageSDK
 func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
  
      //Add your MoEngage Workspace ID and Data center.
      let sdkConfig = MoEngageSDKConfig(appId: "YOUR WorkspaceID", dataCenter: DATA_CENTER);

      // MoEngage SDK Initialization
      // Separate initialization methods for Dev and Prod initializations
      #if DEBUG
          MoEngage.sharedInstance.initializeDefaultTestInstance(sdkConfig)
      #else
         MoEngage.sharedInstance.initializeDefaultLiveInstance(sdkConfig)
      #endif
 
  //Rest of the implementation of method
  //-------
  return true
}

@import MoEngageSDK;
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
     //TODO: Add your MoEngage Workspace ID and Data center.
     MoEngageSDKConfig* sdkConfig = [[MoEngageSDKConfig alloc] initWithAppId:@"YOUR Workspace ID" dataCenter: DATA_CENTER];
    
// MoEngage SDK Initialization
    // Separate initialization methods for Dev and Prod initializations
    #ifdef DEBUG
         [[MoEngage sharedInstance] initializeDefaultTestInstance:sdkConfig];
    #else
         [[MoEngage sharedInstance] initializeDefaultLiveInstance:sdkConfig];
    #endif
    
  //Rest of the implementation of method
  //-------
}

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

MoEngageSDKConfig Properties

Following properties can be configured using the instance of MoEngageSDKConfig for SDK version 9.0.0

Test/Live Environment

As mentioned above while initializing the build, MoEngage SDK makes use of the DEBUG preprocessor macro to decide whether the build is meant for TEST/LIVE Environment. Therefore you will have to take care of the same while generating the build and make sure that the Build Configuration of the App's target is set as mentioned below:

• For Development Build: Build Configuration should be set to Debug (Data will be tracked in TEST Environment)
• For AdHoc Build/App Store Build: Build Configuration should be set to Release (Data will be tracked in LIVE Environment)

How to set Build Configuration?

Build Configuration on Running the app from Xcode:

Whenever you run the app directly from Xcode without archiving, make sure the build configuration of Run mode of the App Target in Edit Scheme is set to Debug(set by default settings). Doing this will make sure data is tracked in TEST Environment.

Build Configuration on Exporting the build:

While exporting the build make sure you set the correct Build Configuration. By default for Archive section in Edit Scheme the Build Configuration will be set to Release, but for a development build make sure its changed to Debug before exporting the build. To set the Build Configuration of the build in your Xcode project go to App Target > Edit Scheme > Archive > Build Configuration and set the configuration to Debug/Release(depending on the type of build). Refer to the image as described:

Switching Environment in Dashboard

In the MoEngage dashboard you can switch between test and live environment for your app. 

TEST Environment is used for all the development and testing-related uses and LIVE environment is used for running all the campaigns for AppStore Builds for your app's user base.