You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d39e93a
Browse filesBrowse the repository at this point in the historyBrowse files
feat(android): Report app start reason on standalone app start transaction
Read ApplicationStartInfo.getReason() (API 35+) and attach it as
app.start.reason trace data on the standalone app.start transaction
in both the foreground and headless paths.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@
9
9
- Emits a transaction named `App Start` with op `app.start`, carrying the existing app start measurements and phase spans (`process.load`, `contentprovider.load`, `application.load`, activity lifecycle spans) as direct children of the root
10
10
- The standalone transaction shares the same `traceId` as the first `ui.load` activity transaction so they remain linked in the trace view
11
11
- Also covers non-activity starts (broadcast receivers, services, content providers)
12
+
- On Android 15+ (API 35), the standalone transaction reports why the OS started the process via `app.start.reason` trace data (e.g. `launcher`, `broadcast`, `service`, `content_provider`), derived from `ApplicationStartInfo.getReason()`
0 commit comments