Debug
or Verbose
log levels may cause performance or security concerns. As a result, it is recommended that you use only Error
or Warning
log levels in production applications.onResume
function, start Lifecycle data collection:Activity
has no negative impact and ensures that the SDK always has the necessary reference to your application. As a result, you should call setApplication
on each of your activities.onPause
function to pause the lifecycle data collection:Activity
.lifecycleStart:
from within the callback of the ACPCore::start:
method in your app's application:didFinishLaunchingWithOptions:
delegate method.application:didFinishLaunchingWithOptions:
method may 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
.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:
:applicationDidEnterBackground:
delegate method:lifecycleStart:
from within the callback of the ACPCore::start:
method in your app's application:didFinishLaunchingWithOptions:
delegate method.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
.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:
:applicationDidEnterBackground:
delegate method: