Skip to content

fix(apple): Note on pre warmed app starts #5169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 20, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ To enable this feature enable `AutoUIPerformanceTracking`. The SDK differentiate
* __Cold start__: App launched for the first time, after a reboot or update. The app is not in memory and no process exists.
* __Warm start__: App launched at least once, is partially in memory, and no process exists.

The SDK uses the process start time as the beginning of the app start and the [`UIWindowDidBecomeVisibleNotification`][UIWindow] as the end. It creates the following spans:
The SDK uses the process start time as the beginning of the app start and the [`UIWindowDidBecomeVisibleNotification`][UIWindow] as the end. Since iOS 15, the system might decide to pre-warm your app by already creating the process before the user opens it. In such cases, we can't reliably measure the app start, and we drop it. The SDK creates the following spans:
* __Pre Main__: From the process start time to the runtime init.
* __UIKit and Application Init__: From the runtime init to the [`didFinishLaunchingNotification`][didFinishLaunching].
* __Initial Frame Render__: From the [`didFinishLaunchingNotification`][didFinishLaunching] to [`UIWindowDidBecomeVisibleNotification`][UIWindow].
Expand Down