Skip to content

updated when the cold start span is finished on Android (first frame … #11399

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.

Sign up for GitHub

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
Sep 19, 2024
Merged

updated when the cold start span is finished on Android (first frame … #11399

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 6 additions & 6 deletions docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ _The Activity's instrumentation is enabled by default, but you may disable it by
</application>
```

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:_

Expand Down Expand Up @@ -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.

<Note>

Expand Down Expand Up @@ -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("<tag>")` 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("<tag>")` 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
Expand All @@ -299,7 +299,7 @@ fun LoginScreen() {

<Note>

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.

</Note>
Expand All @@ -312,8 +312,8 @@ The Sentry Kotlin Compiler plugin is considered _experimental_. Give it a try an

</Note>

The <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink> can automatically enrich your `@Composable` functions during compilation with a tag name,
based on the function name of your `@Composable`.
The <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink> 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}
Expand Down