Lifecycle extension in Android

Implementing Lifecycle Metrics in Android

Tracking app crashes in Android

This information helps you understand how crashes are tracked and the best practices to handle false crashes.
Important: App crashes are tracked as part of lifecycle metrics. Before you can track crashes, add the library to your project. For more information about implementing lifecycle, see Implementing Lifecycle Metrics in Android.
When lifecycle metrics are implemented, a call is made to MobileCore.lifecycleStart(additionalContextData) in the OnResume method of each activity. In the onPause method, a call is made to MobileCore.lifecyclePause(). In the MobileCore.lifecyclePause() method, a flag is set to indicate a graceful exit. When the app is launched again or resumed, MobileCore.lifecycleStart(additionalContextData) checks this flag. If the app did not exit successfully as determined by the flag status, an a.CrashEvent context data is sent with the next call, and a crash event is reported.
Important: To ensure accurate crash reporting, you must call lifecyclePause() in the onPause method of each activity.
To understand why this is essential, here is an illustration of the Android activity lifecycle:
For more information about the Android activity lifecycle, see Activities.
This Android lifecycle illustration was created and shared by the Android Open Source Project and used according to terms in the Creative Commons 2.5 Attribution License.
What can cause a false crash to be reported?
  • If you are debugging by using an IDE, such as Android Studio, and launching the app again from the IDE while the app is in the foreground causes a crash.
    Tip: You can avoid this crash by backgrounding the app before launching again from the IDE.
  • If the previous foreground Activity of your app is moved to the background and does not call MobileCore.lifecyclePause()in onPause, and your app is manually closed or killed by the operating system, the next launch results in a crash.
How should Fragments be handled?
Fragments have application lifecycle events that are similar to Activities. However, a Fragment cannot be active without being attached to an Activity.

Implementing Global Lifecycle Callbacks

Starting with API Level 14, Android allows global lifecycle callbacks for activities. For more information, see the Android Developers Guide.
You can use these callbacks to ensure that all of your Activities correctly call AdobeMobileMarketing.lifecycleStart(), and do not need to implement the code for each of the Activity.
public class MainActivity extends Activity {
protected void onCreate(Bundle savedInstanceState) {
getApplication().registerActivityLifecycleCallbacks(new Application.ActivityLifecycleCallbacks() {
public void onActivityResumed(Activity activity) {
public void onActivityPaused(Activity activity) {
// the following methods aren't needed for our lifecycle purposes, but are
// required to be implemented by the ActivityLifecycleCallbacks object
public void onActivityCreated(Activity activity, Bundle savedInstanceState) {}
public void onActivityStarted(Activity activity) {}
public void onActivityStopped(Activity activity) {}
public void onActivitySaveInstanceState(Activity activity, Bundle outState) {}
public void onActivityDestroyed(Activity activity) {}
To include additional data with lifecycle metric calls, pass an additional parameter to lifecycleStart that contains context data:
void onResume() {
HashMap<String, Object> additionalContextData = new HashMap<String, Object>();
contextData.put("myapp.category", "Game");
Important: You need to add this code only in your main Activity and any other Activity in which your app may be launched.