React Native

The MOVE SDK can be initialized natively or through Javascript. For the first init, the SDK expects to be initialized after user onboarding using Javascript. In this case, Javascript passes the required MoveAuth and MoveConfig objects.

In all future inits, the SDK expects to be initialized natively at app start points (In Appdelegate for iOS, and MainApplication for Android). This is to guarantee that the MOVE SDK is set up and active before the limited time provided by the OS in background wakeups is consumed.

The native init will re-use the last authentication and configs objects passed to the SDK from the JS initialization.


To initialize the SDK natively, in your Appdelegate:

@implementation AppDelegate
  - (BOOL)application:(UIApplication *)application willFinishLaunchingWithOptions:(NSDictionary *)launchOptions
    [DolphinSdk initIfPossibleWithLaunchOptions:launchOptions];
    return YES;

We strongly recommend against loading UI in background wakeups, but only when it is a foreground wakeup or when the user brings the app to the foreground.

if([application applicationState] == UIApplicationStateInactive) {
    [self launchUI];
- (void)applicationWillEnterForeground:(UIApplication *)application {
  if(rootView == nil) {
    [self launchUI];


To initialize the SDK natively, in your MainApplication:

import in.dolph.move.sdk.NativeMoveSdkWrapper;

public class MainApplication extends Application implements ReactApplication {
  private NativeMoveSdkWrapper sdkWrapper;

  public void onCreate() {
    sdkWrapper = NativeMoveSdkWrapper.getInstance(this);
    if (sdkWrapper.isNativeInitializationEnabled()) {
    try {
    } catch (Throwable t) {
      // handle init Configuration Errors


initialize: (
    config: MoveSdkConfig,
    auth: MoveSdkAuth,
    android: MoveSdkAndroidConfig
  ) => void



The required SDK configurations.


The user's Auth object.


The launch options passed inwillFinishLaunchWithOptions.

The MOVE SDK needs to be initialized before willFinishLaunchingWithOptions() returns in iOS and before onCreate()returns in Android. This guarantees that all the required SDK components are initialized and ready to handle the triggered system events.

In case the app has a login flow, you may want to delay the SDK initialization until the login process is complete. In that case, the app could start the SDK through JavaScript. Once the user is logged in, the SDK should always start before the end ofonCreate()or willFinishLaunchingWithOptions()returns.

Last updated