feat(tracing): Track appLoaded and extendAppStart adoption#6426
Merged
antonis merged 2 commits intoJul 10, 2026
Conversation
Register a no-op `GlobalErrorBoundary` integration when the component mounts so the name flows through to `event.sdk.integrations` — the same channel used for feature- adoption signals like `MobileFeedback` and `AppStart`. Also introduces a shared `registerFeatureMarker` helper. Subsequent markers for other opt-in features (NavigationContainer, ExpoRouter error boundary, AppLoaded, ...) will use this helper — see #6415. Refs: #6415
Register no-op `AppLoaded` and `ExtendedAppStart` integrations on first call so the names flow through to `event.sdk.integrations`. `ExtendedAppStart` covers all three extend API entry points: `extendAppStart`, `getExtendedAppStartSpan`, and `finishExtendedAppStart`. Refs: #6415
Contributor
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
🤖 This preview updates automatically when you update the PR. |
Contributor
|
📲 Install BuildsAndroid
|
Contributor
iOS (legacy) Performance metrics 🚀
|
Base automatically changed from
feat/track-global-error-boundary-adoption
to
main
July 10, 2026 06:08
antonis
deleted the
feat/track-app-loaded-and-extended-app-start-adoption
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of change
Description
Registers no-op
AppLoadedandExtendedAppStartintegrations on first call so the names flow through toevent.sdk.integrations.ExtendedAppStartcovers all three extend API entry points:extendAppStart,getExtendedAppStartSpan, andfinishExtendedAppStart.Bundled together because both markers live in
packages/core/src/js/tracing/integrations/appStart.ts— splitting them into separate PRs would produce mechanical merge conflicts on the shared imports.Motivation and Context
Part of #6415.
Sentry.appLoaded()explicitly signals app-start end but leaves no distinctive event fingerprint today.Sentry.extendAppStart()/getExtendedAppStartSpan()/finishExtendedAppStart()are new experimental APIs that produce standalone app-start transactions indistinguishable from auto-captured ones.How did you test it?
test/tracing/integrations/appStart.test.ts: anAppLoadedmarker test in the existingappLoaded() APIdescribe block and a parameterizedit.eachfor the threeExtendedAppStartentry points.Note on semantics
ExtendedAppStartfires even if the underlying integration no-ops (e.g., user calledextendAppStartwithout enabling_experiments.enableStandaloneAppStartTracing). This is intentional — measures API adoption, not just successful use.Checklist
sdk.integrationsmarkers #6415)Base
Stacked on top of #6421. When #6421 merges, GitHub will automatically retarget this PR to
main.Refs: #6415