Debugging & lifecycle metrics

Debug logging
Debug logging is an optional, yet a recommended and critical SDK feature.
By enabling logging, you can ensure that the SDK is working as intended. The following table explains levels of logging available and the purpose they serve:
Log Level
Description
Error
This is the default log level used by SDK. This log level provides the details about unrecoverable errors that occurred during SDK implementation.
Warning
In addition to the detail from Error log level, Warning provides error information during SDK integration. This log level might indicate that a request has been made to the SDK, but the SDK might be unable to perform the requested task. For example, this log level might be used when catching an unexpected, but recoverable, exception and printing its message.
Debug
In addition to detail from the Warning log level, Debug also provides high-level information about how the SDK processes network requests/responses data.
Verbose
In addition to detail from the Debug level, Verbose provides detailed, low-level information about how SDK processes database interactions and SDK events.
Note that using Debug or Verbose log levels may cause performance or security concerns. It is recommended that you use only Error or Warning log levels in production applications.
To enable debug logging, use the following methods:
Android
iOS - Swift
iOS - Obj C
React Native
Flutter
Cordova
Unity
Android
Java
MobileCore.setLogLevel(LoggingMode.DEBUG);
// MobileCore.setLogLevel(LoggingMode.VERBOSE);
// MobileCore.setLogLevel(LoggingMode.WARNING);
// MobileCore.setLogLevel(LoggingMode.ERROR);
iOS - Swift
Swift
// AEPCore.setLogLevel(AEPMobileLogLevel.debug)
// AEPCore.setLogLevel(AEPMobileLogLevel.verbose)
// AEPCore.setLogLevel(AEPMobileLogLevel.warning)
// AEPCore.setLogLevel(AEPMobileLogLevel.error)
Objective-C
// [AEPCore setLogLevel:AEPMobileLogLevelDebug];
// [AEPCore setLogLevel:AEPMobileLogLevelVerbose];
// [AEPCore setLogLevel:AEPMobileLogLevelWarning];
// [AEPCore setLogLevel:AEPMobileLogLevelError];
iOS - Obj C
Objective-C
[ACPCore setLogLevel:ACPMobileLogLevelDebug];
// [ACPCore setLogLevel:ACPMobileLogLevelVerbose];
// [ACPCore setLogLevel:ACPMobileLogLevelWarning];
// [ACPCore setLogLevel:ACPMobileLogLevelError];
Swift
ACPCore.setLogLevel(ACPMobileLogLevel.debug)
// ACPCore.setLogLevel(ACPMobileLogLevel.verbose)
// ACPCore.setLogLevel(ACPMobileLogLevel.warning)
// ACPCore.setLogLevel(ACPMobileLogLevel.error)
React Native
Javascript
ACPCore.setLogLevel(ACPMobileLogLevel.DEBUG);
//ACPCore.setLogLevel(ACPMobileLogLevel.VERBOSE);
//ACPCore.setLogLevel(ACPMobileLogLevel.WARNING);
//ACPCore.setLogLevel(ACPMobileLogLevel.ERROR);
Flutter
Dart
FlutterACPCore.setLogLevel(ACPLoggingLevel.DEBUG);
//FlutterACPCore.setLogLevel(ACPLoggingLevel.VERBOSE);
//FlutterACPCore.setLogLevel(ACPLoggingLevel.WARNING);
//FlutterACPCore.setLogLevel(ACPLoggingLevel.ERROR);
Cordova
Cordova
Controlling the log level of the SDK
ACPCore.setLogLevel(ACPCore.ACPMobileLogLevelError, successCallback, errorCallback);
ACPCore.setLogLevel(ACPCore.ACPMobileLogLevelWarning, successCallback, errorCallback);
ACPCore.setLogLevel(ACPCore.ACPMobileLogLevelDebug, successCallback, errorCallback);
ACPCore.setLogLevel(ACPCore.ACPMobileLogLevelVerbose, successCallback, errorCallback);
Unity
C#
Controlling the log level of the SDK
ACPCore.SetLogLevel(ACPCore.ACPMobileLogLevel.ERROR);
ACPCore.SetLogLevel(ACPCore.ACPMobileLogLevel.WARNING);
ACPCore.SetLogLevel(ACPCore.ACPMobileLogLevel.DEBUG);
ACPCore.SetLogLevel(ACPCore.ACPMobileLogLevel.VERBOSE);
Lifecycle metrics
Lifecycle metrics is an optional, yet valuable feature provided by the Adobe Experience Platform SDK. It provides out-of-the-box, application lifecycle information about your app user. A complete list of available metrics is provided here.
These metrics contain information on the app user's engagement lifecycle such as device information, install or upgrade information, session start and pause times, and so on. You may also set additional lifecycle metrics.
This section shows you how to collect lifecycle metrics. To view, and report on this data in those respective solutions, you need to set up Analytics or other Experience Cloud solution extensions.
Lifecycle metrics are not available for Edge Network at this time. Check back soon on support for XDM-based lifecycle metrics for Edge Network implementations.
Android
iOS - Obj C
React Native
Flutter
Cordova
Unity
Xamarin
Android
Java
With the onResume function, start Lifecycle data collection:
@Override  
   public void onResume() {  
      MobileCore.setApplication(getApplication());
      MobileCore.lifecycleStart(null);
   }
Setting the application is only necessary on activities that are entry points for your application. However, setting the application on each Activity has no negative impact and ensures that the SDK always has the necessary reference to your application. We recommend that you call setApplicationin each of your activities.
You can use the onPause function to pause the lifecycle data collection:
To ensure accurate session and crash reporting, this call must be added to every activity.
@Override
   public void onPause() {
      MobileCore.lifecyclePause();
   }
iOS - Obj C
Objective-C
Start Lifecycle data collection by calling lifecycleStart: from within the callback of the ACPCore::start: method in your app's application:didFinishLaunchingWithOptions: delegate method.
If your iOS application supports background capabilities, your application:didFinishLaunchingWithOptions: method might be called when iOS launches your app in the background. If you do not want background launches to count towards your lifecycle metrics, then lifecycleStart: should only be called when the application state is not equal to UIApplicationStateBackground.
- (BOOL) application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    // register the lifecycle extension
    [ACPLifecycle registerExtension];
​
    const UIApplicationState appState = application.applicationState;
    [ACPCore start:^{
        // only start lifecycle if the application is not in the background
        if (appState != UIApplicationStateBackground) {
            [ACPCore lifecycleStart:nil];
        }
    }];
}
When launched, if your app is resuming from a backgrounded state, iOS might call your applicationWillEnterForeground: delegate method. You also need to call lifecycleStart:, but this time you do not need all of the supporting code that you used in application:didFinishLaunchingWithOptions::
- (void) applicationWillEnterForeground:(UIApplication *)application {
    [ACPCore lifecycleStart:nil];
}
When the app enters the background, pause Lifecycle data collection from your app's applicationDidEnterBackground: delegate method:
 - (void) applicationDidEnterBackground:(UIApplication *)application {
    [ACPCore lifecyclePause];
 }
Swift
Start Lifecycle data collection by calling lifecycleStart: from within the callback of the ACPCore::start: method in your app's application:didFinishLaunchingWithOptions: delegate method.
If your iOS application supports background capabilities, your application:didFinishLaunchingWithOptions: method might be called when iOS launches your app in the background. If you do not want background launches to count towards your lifecycle metrics, then lifecycleStart: should only be called when the application state is not equal to UIApplicationStateBackground.
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
    // register the lifecycle extension
    ACPLifecycle.registerExtension();
​
    let appState = application.applicationState;            
    ACPCore.start {
        // only start lifecycle if the application is not in the background    
        if appState != .background {
            ACPCore.lifecycleStart(nil)
        }    
    }    
}
When launched, if your app is resuming from a backgrounded state, iOS might call your applicationWillEnterForeground: delegate method. You also need to call lifecycleStart:, but this time you do not need all of the supporting code that you used in application:didFinishLaunchingWithOptions::
func applicationWillEnterForeground(_ application: UIApplication) {    
    ACPCore.lifecycleStart(nil)
}
When the app enters the background, pause Lifecycle data collection from your app's applicationDidEnterBackground: delegate method:
func applicationDidEnterBackground(_ application: UIApplication) {    
    ACPCore.lifecyclePause()
}
React Native
JavaScript
Note: We recommend implementing Lifecycle metrics in native code, however, Lifecycle API's are available in Javascript if it fits your use case.
Starting a lifecycle event
ACPCore.lifecycleStart({"lifecycleStart": "myData"});
Pausing a lifecycle event
ACPCore.lifecyclePause();
Flutter
Flutter
Note: It is required to implement Lifecycle in native Android and iOS code.
Cordova
Cordova
Note: We recommend implementing Lifecycle in native Android and iOS code.
Getting Lifecycle version:
ACPLifecycle.extensionVersion(function(version) {
    console.log(version);
}, function(error) {
    console.log(error);
});
Unity
C#
Starting and pausing a lifecycle event
private void OnApplicationPause(bool pauseStatus)
{
  if (pauseStatus)
  {
    ACPCore.LifecyclePause();
  }
  else
  {
    var cdata = new Dictionary<string, string>();
    cdata.Add("launch.data", "added");
    ACPCore.LifecycleStart(cdata);
  }
}
Xamarin
C#
iOS
Starting and pausing a lifecycle event
public override void WillEnterForeground(UIApplication uiApplication)
{
  base.WillEnterForeground(uiApplication);
  ACPCore.LifecycleStart(null);
}
​
public override void DidEnterBackground(UIApplication uiApplication)
{
  base.DidEnterBackground(uiApplication);
  ACPCore.LifecycleStart(null);
}
Android
Starting and pausing a lifecycle event
protected override void OnResume()
{
  base.OnResume();
  ACPCore.LifecycleStart(null);
}
​
protected override void OnPause()
{
  base.OnPause();
  ACPCore.LifecyclePause();
}
For more information, see Lifecycle Metrics.
Getting Started - Previous
Get the Experience Platform SDK
Next - Getting Started
Track events
Last updated 3 days ago
Log Level	Description
Error	This is the default log level used by SDK. This log level provides the details about unrecoverable errors that occurred during SDK implementation.
Warning	In addition to the detail from Error log level, Warning provides error information during SDK integration. This log level might indicate that a request has been made to the SDK, but the SDK might be unable to perform the requested task. For example, this log level might be used when catching an unexpected, but recoverable, exception and printing its message.
Debug	In addition to detail from the Warning log level, Debug also provides high-level information about how the SDK processes network requests/responses data.
Verbose	In addition to detail from the Debug level, Verbose provides detailed, low-level information about how SDK processes database interactions and SDK events.