React Native Lifecycle and Identity

React Native exposes a single entrypoint: AppActor.instance.

Use the singleton

import { AppActor } from 'appactor-react-native';

await AppActor.instance.configure('pk_YOUR_PUBLIC_APP_KEY', {
  appUserId: 'user_123',
});

Do not instantiate the class yourself. The package guards against direct construction and expects the singleton pattern.

Configure rules

configure once as part of app startup
pass either one key or platform-specific keys
use options for wrapper-level behavior such as log level

Use platform-specific keys

Use AppActorPlatformKeys when your AppActor project has separate iOS and Android apps.

import { AppActor, AppActorPlatformKeys } from 'appactor-react-native';

await AppActor.instance.configure(
  new AppActorPlatformKeys(
    'pk_YOUR_IOS_PUBLIC_APP_KEY',
    'pk_YOUR_ANDROID_PUBLIC_APP_KEY'
  ),
  { appUserId: 'user_123' }
);

The wrapper chooses the iOS key on iOS and the Android key on Android. Unsupported platforms throw instead of guessing.

Identity methods

logIn(appUserId)
logOut()
getAppUserId()
getIsAnonymous()
reset()
sdkVersion()
setLogLevel(...)

Platform startup helpers

register enableSearchAdsTracking() before wrapper configure on iOS if you want Apple Ads tracking enabled during startup
call enableInstallReferrer() after configure on Android

The wrapper registers ASA intent early, while the native iOS helper still runs after native configure is ready. See React Native Apple Search Ads.

SDK logs

The package also exposes onSdkLog, which is useful when debugging bridge-level behavior without stepping into native code immediately.

​Use the singleton

​Configure rules

​Use platform-specific keys

​Identity methods

​Platform startup helpers

​SDK logs