Repository navigation
Conversation
Remove the experimental annotations from Sentry.startProfiler and Sentry.stopProfiler. The process-global lifecycle API is stable across the JVM and Android profiler implementations, while platform-specific improvements can continue internally. Refs #6408 Refs #4778 Refs #5906 Co-Authored-By: Claude <noreply@anthropic.com>
📲 Install BuildsAndroid
|
adinauer
marked this pull request as ready for review
October 30, 2026 09:34
adinauer
requested review from
0xadam-brown,
markushi,
romtsn and
runningcode
as code owners
October 30, 2026 09:34
This branch has not been deployed
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
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.
📜 Description
Remove
@ApiStatus.Experimentalfrom the continuous profiling lifecycle APIs:Sentry.startProfiler()Sentry.stopProfiler()Internal profiler interfaces and platform implementations remain unchanged. This changes API status only; profiling behavior remains unchanged.
💡 Motivation and Context
The static start/stop lifecycle is documented for both Java and Android and is shared across the JVM async-profiler and Android profiling implementations. Platform-specific collection and upload improvements can continue behind this stable process-global API.
JVM profiling remains unavailable on Windows, and Android framework profiling requests may be rejected asynchronously. Follow-up work remains tracked in #4778 and #5906 without requiring a public API redesign.
Refs #6408
💚 How did you test it?
Ran:
Both commands completed successfully, and API generation produced no API dump changes.
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Continue improving platform support, diagnostics, and profiler-ID handling behind the stable lifecycle API.