Bump io.sentry:sentry-android-core from 8.50.1 to 8.51.0

[dependabot]

Bumps io.sentry:sentry-android-core from 8.50.1 to 8.51.0.

Release notes

Sourced from io.sentry:sentry-android-core's releases.

8.51.0

Features

• Use Android's ProfilingManager (Perfetto) for continuous profiling on API 35+ devices (#5251)
  • On API 35+ devices, continuous profiling now automatically uses Android's system ProfilingManager with Perfetto-based stack sampling, providing lower-overhead and more accurate profiles. No configuration change is required.
  • Devices below API 35 keep using the legacy Debug-based profiler.
  • Added an enableLegacyProfiling option (default true) to disable the legacy Debug-based profiler. Setting it to false disables continuous profiling on API < 35 devices as well as transaction-based profiling (profilesSampleRate/profilesSampler) on all devices, since transaction-based profiling is not supported by Perfetto.
  • It can also be configured via the io.sentry.profiling.enable-legacy-profiling manifest flag.
  • See the Android profiling docs for details.

Behavioral Changes

• The outbox and cache directories are no longer created by Sentry.init (#5792)
  • They are now created lazily by whichever component first writes into them, off the init thread. As a result, the directories at SentryOptions.getOutboxPath() and SentryOptions.getCacheDirPath() are not guaranteed to exist once Sentry.init returns.
  • If you write envelopes into the outbox path yourself instead of going through the SDK — as hybrid SDKs do for captureEnvelope — create the directory first, e.g. new File(outboxPath).mkdirs().

Improvements

• Skip building Android manifest metadata debug log messages when debug logging is disabled, reducing allocations during SDK init (#5790)

Fixes

• Use the original app build's ProGuard UUID for ANR profile chunks (#5852)
• Fix potential ANR/deadlock in Session Replay when checkCanRecord runs on the replay executor thread (#5837)
• Prevent concurrent PixelCopy access during Session Replay masking and bitmap cleanup (#5808)
• Release MediaMuxer when the replay video encoder fails to start to avoid a resource leak (#5607)
• Set the correct platform (android instead of java) on ANR profile chunks so they are billed as UI Profile Hours rather than Continuous Profile Hours (#5836)
• Skip encoding and capturing buffered session replay segments while rate-limited, so we don't waste resources on envelopes the transport will drop (#5813)
  • These skipped replays are now reported as ratelimit_backoff discarded events in client reports, so they no longer disappear from drop statistics. One event is recorded per buffer flush rather than per segment.
  • Buffer mode is also kept while rate-limited instead of switching to session mode, so the rolling buffer stays warm and the next error after the rate limit expires can send a complete replay.

Performance

• Create the outbox and cache directories lazily in their consumers instead of during SDK init, moving the mkdirs() calls off the init (main) thread (#5792)
• Reduce the number of SDK threads: LifecycleWatcher now schedules the session-end task on the shared timer executor instead of creating a dedicated java.util.Timer thread (#5819)
• Reduce the number of SDK threads: RateLimiter now schedules its rate-limit-lifted notifications on the shared timer executor instead of creating a dedicated java.util.Timer thread (#5814)
• Speed up deserialization of arbitrary JSON objects by typing numbers without throwing exceptions (#5783)

Dependencies

• Bump Native SDK from v0.15.4 to v0.16.0 (#5845)
  • changelog
  • diff

Changelog

Sourced from io.sentry:sentry-android-core's changelog.

8.51.0

Features

• Use Android's ProfilingManager (Perfetto) for continuous profiling on API 35+ devices (#5251)
  • On API 35+ devices, continuous profiling now automatically uses Android's system ProfilingManager with Perfetto-based stack sampling, providing lower-overhead and more accurate profiles. No configuration change is required.
  • Devices below API 35 keep using the legacy Debug-based profiler.
  • Added an enableLegacyProfiling option (default true) to disable the legacy Debug-based profiler. Setting it to false disables continuous profiling on API < 35 devices as well as transaction-based profiling (profilesSampleRate/profilesSampler) on all devices, since transaction-based profiling is not supported by Perfetto.
  • It can also be configured via the io.sentry.profiling.enable-legacy-profiling manifest flag.
  • See the Android profiling docs for details.

Behavioral Changes

• The outbox and cache directories are no longer created by Sentry.init (#5792)
  • They are now created lazily by whichever component first writes into them, off the init thread. As a result, the directories at SentryOptions.getOutboxPath() and SentryOptions.getCacheDirPath() are not guaranteed to exist once Sentry.init returns.
  • If you write envelopes into the outbox path yourself instead of going through the SDK — as hybrid SDKs do for captureEnvelope — create the directory first, e.g. new File(outboxPath).mkdirs().

Improvements

• Skip building Android manifest metadata debug log messages when debug logging is disabled, reducing allocations during SDK init (#5790)

Fixes

• Use the original app build's ProGuard UUID for ANR profile chunks (#5852)
• Fix potential ANR/deadlock in Session Replay when checkCanRecord runs on the replay executor thread (#5837)
• Prevent concurrent PixelCopy access during Session Replay masking and bitmap cleanup (#5808)
• Release MediaMuxer when the replay video encoder fails to start to avoid a resource leak (#5607)
• Set the correct platform (android instead of java) on ANR profile chunks so they are billed as UI Profile Hours rather than Continuous Profile Hours (#5836)
• Skip encoding and capturing buffered session replay segments while rate-limited, so we don't waste resources on envelopes the transport will drop (#5813)
  • These skipped replays are now reported as ratelimit_backoff discarded events in client reports, so they no longer disappear from drop statistics. One event is recorded per buffer flush rather than per segment.
  • Buffer mode is also kept while rate-limited instead of switching to session mode, so the rolling buffer stays warm and the next error after the rate limit expires can send a complete replay.

Performance

• Create the outbox and cache directories lazily in their consumers instead of during SDK init, moving the mkdirs() calls off the init (main) thread (#5792)
• Reduce the number of SDK threads: LifecycleWatcher now schedules the session-end task on the shared timer executor instead of creating a dedicated java.util.Timer thread (#5819)
• Reduce the number of SDK threads: RateLimiter now schedules its rate-limit-lifted notifications on the shared timer executor instead of creating a dedicated java.util.Timer thread (#5814)
• Speed up deserialization of arbitrary JSON objects by typing numbers without throwing exceptions (#5783)

Dependencies

• Bump Native SDK from v0.15.4 to v0.16.0 (#5845)
  • changelog
  • diff

Commits

• b01b159 release: 8.51.0
• 1c74da0 chore(changelog): Fix Changelog (#5868)
• 7055ed1 feat(profiling): Add Android ProfilingManager (Perfetto) support (#5251)
• 80c3e67 build: Replace Gradle APIs removed in Gradle 10 (#5864)
• 1b40080 fix(anr): Use Proguard ID from origination ANR process with ANR profie chunks...
• 91e71ac build: Upgrade Gradle to 9.6.1 (#5863)
• 8f86119 fix(anr-profiling): Properly bill ANR profiling under UI Profile Hours (#5836)
• 5e6844d perf(core): Create outbox and cache dirs lazily instead of during init (JAVA-...
• c318acd perf: Schedule rate-limit notifications on shared executor (JAVA-653) (#5814)
• d1f9ed4 chore(deps): bump the github-actions group across 1 directory with 3 updates ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Warning

Review limit reached

@dependabot[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 062683b8-0cc2-4c09-9ff8-5263a0350aca

📥 Commits

Reviewing files that changed from the base of the PR and between 644989c and e762f73.

📒 Files selected for processing (1)

• gradle/libs.versions.toml

---

_{Comment @coderabbitai help to get the list of available commands.}