Multi-process apps

Android applications can consist of one or more processes. You can choose to run your services or activities in a process other than the main one. You implement this by setting android:process property inside your process or activity definition in the Android manifest file.

<activity
  android:name=".YourActivity"
  android:process=":YourProcessName">
</activity>

<service
  android:name=".YourService"
  android:process=":YourProcessName">
</service>

By defining your services or activities like this, you are forcing them to run in a different process than the main one.

By default, the name of your main process is the same as your app package name. If your app package name is com.example.myapp, that will also be the name of your main process. In that case, YourActivity and YourService will run in a process named com.example.myapp:YourProcessName.

The Adtrace SDK does not currently support tracking from more than one process in an app. If you are using multiple processes in your app, you should set the main process name in the AdTraceConfig object.

String appToken = "{YourAppToken}";
String environment = AdTraceConfig.ENVIRONMENT_SANDBOX;  // or AdTraceConfig.ENVIRONMENT_PRODUCTION

AdTraceConfig config = new AdTraceConfig(this, appToken, environment);
config.setProcessName("com.example.myapp");

AdTrace.onCreate(config);

You can also change the name of your main process by changing the android:process property of your application in the Android manifest file.

<application
  android:name=".YourApp"
  android:icon="@drawable/ic_launcher"
  android:label="@string/app_name"
  android:theme="@style/AppTheme"
  android:process=":YourMainProcessName">
</application>

If you name your main process like this, then you should set your main process name in AdTraceConfig object like this:

config.setProcessName("com.example.myapp:YourMainProcessName");

This will inform our SDK of your main process name, so that the SDK will not initialize in any other process where you might try to use it. If you try to use the SDK from some other process, you will get the following log message:

05-06 17:15:06.885    8743-8743/com.example.myapp:YourProcessName
I/AdTrace﹕ Skipping initialization in background process (com.example.myapp:YourProcessName)

If you do not set your main process name in the AdTraceConfig object and then try to call the SDK in multiple processes, you will initialize several different instances of the SDK, as different processes in Android do not share the same memory space. This can lead to some unpredictability, so we strongly advise you to always set your main process name if you have a multi-process app, or ensure that you do not use the Adtrace SDK in more than one process in your app.