Skip to content

Commit bd0a0f8

Browse files
buenaflorclaude
andcommitted
docs(options): Clarify standalone app start javadoc per review
- Use plain quotes for the "App Start" transaction name instead of {@code} - Clarify that the API 35 gate refers to the device's runtime OS version Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent 758727a commit bd0a0f8

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

‎sentry-android-core/src/main/java/io/sentry/android/core/SentryAndroidOptions.java‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -697,19 +697,19 @@ public boolean isEnableStandaloneAppStartTracing() {
697697
* <p>The SDK reports app start through these paths:
698698
*
699699
* <ul>
700-
* <li>With an Activity: the SDK sends an {@code App Start} transaction with operation {@code
700+
* <li>With an Activity: the SDK sends an "App Start" transaction with operation {@code
701701
* app.start}, plus a separate {@code ui.load} transaction for the Activity. Both
702702
* transactions share the same trace ID.
703703
* <li>Headless app start: for launches started by something like a broadcast receiver, service,
704704
* or content provider without an Activity, the SDK sends only the standalone app-start
705705
* transaction.
706706
* <ul>
707-
* <li>On Android API 35 and newer, the SDK can use {@code ApplicationStartInfo} to
708-
* classify cold versus warm starts and find the {@code Application.onCreate} end
709-
* time.
710-
* <li>Before Android API 35, headless launches are treated as cold once {@code
711-
* Application.onCreate} finishes without an Activity. The end time falls back to the
712-
* best SDK/plugin timing available.
707+
* <li>On devices running Android 15 (API level 35) or newer, the SDK can use {@code
708+
* ApplicationStartInfo} to classify cold versus warm starts and find the {@code
709+
* Application.onCreate} end time.
710+
* <li>On devices running older Android versions, headless launches are treated as cold
711+
* once {@code Application.onCreate} finishes without an Activity. The end time falls
712+
* back to the best SDK/plugin timing available.
713713
* <li>With {@code Application.onCreate} instrumentation, the SDK can add an {@code
714714
* application.load} phase span and use the exact {@code Application.onCreate} end
715715
* time. Without that instrumentation, the standalone transaction is still sent, but

0 commit comments

Comments
 (0)