From 711b9502ecc7915f92c11c022756f4f4e6779a2f Mon Sep 17 00:00:00 2001 From: stefanosiano Date: Thu, 19 Sep 2024 17:44:20 +0200 Subject: [PATCH] updated when the cold start span is finished on Android (first frame drawn instead of Activity.onResume callback) --- .../instrumentation/automatic-instrumentation.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx index f549237fb8eac..a0eae2d37de1b 100644 --- a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx @@ -26,7 +26,7 @@ _The Activity's instrumentation is enabled by default, but you may disable it by ``` -The transaction finishes after each Activity's `onResume` method is executed. +The transaction finishes after each Activity's first frame is drawn. _The transaction finishes automatically, but you may disable it by setting:_ @@ -131,7 +131,7 @@ The SDK differentiates between a cold and a warm start, but doesn't track hot st The SDK sets the Span operation to `app.start.cold` for _Cold start_ and `app.start.warm` for _Warm start_. -The SDK uses the `SentryPerformanceProvider` (ContentProvider) creation time as the beginning of the app start and the first `Activity#onResume` call as the end. +The SDK uses the `SentryPerformanceProvider` (ContentProvider) creation time as the beginning of the app start and the first frame drawn as the end. @@ -278,7 +278,7 @@ If the view doesn't have the `id` assigned, the transaction won't be captured be _(New in version 6.10.0)_ -The SDK composes the transaction name out of the host `Activity` and the `tag` set by way of the `Modifier.sentryTag("")` of the `Composable` (for example, `LoginActivity.login_button`). +The SDK composes the transaction name out of the host `Activity` and the `tag` set by way of the `Modifier.sentryTag("")` of the `Composable` (for example, `LoginActivity.login_button`). The transaction operation is set to `ui.action` plus the interaction type (one of `click`, `scroll`, or `swipe`). ```kotlin @@ -299,7 +299,7 @@ fun LoginScreen() { -If the `@Composable` doesn't have a `sentryTag` modifier applied, the transaction won't be captured because it can't be uniquely identified. +If the `@Composable` doesn't have a `sentryTag` modifier applied, the transaction won't be captured because it can't be uniquely identified. To capture a transaction for the `@Composable`, you must either add a `sentryTag` modifier or enable automatic `@Composable` tagging. @@ -312,8 +312,8 @@ The Sentry Kotlin Compiler plugin is considered _experimental_. Give it a try an -The Sentry Kotlin Compiler Plugin can automatically enrich your `@Composable` functions during compilation with a tag name, -based on the function name of your `@Composable`. +The Sentry Kotlin Compiler Plugin can automatically enrich your `@Composable` functions during compilation with a tag name, +based on the function name of your `@Composable`. In order to use this feature, the Sentry Kotlin Compiler plugin needs to be applied to all modules, which contain `@Composable` elements. ```groovy {filename:app/build.gradle}