fix(core): [Callback Errors 1] Report callback failures

[adinauer]

PR Stack (Callback Errors)

• fix(core): Handle callback errors #6140
• fix(core): [Callback Errors 1] Report callback failures #6141
• ref(core): [Callback Errors 2] Mark SDK-owned event processors #6162
• fix(core): [Callback Errors 3] Drop failed processor data #6142
• fix(core): [Callback Errors 4] Drop failed breadcrumbs #6143
• fix(core): [Callback Errors 5] Handle tracesSampler failures #6163
• fix(core): [Callback Errors 6] Handle profilesSampler failures #6164
• fix(core): [Callback Errors 7] Handle replay sampling failures #6165
• fix(core): [Callback Errors 8] Report dropped profiles #6166
• fix(integrations): [Callback Errors 9] Guard custom callbacks #6167

---

📜 Description

Adds DiscardReason.CALLBACK_ERROR and uses it when an existing beforeSend* callback throws and drops telemetry. Intentional null returns continue to use before_send.

The change preserves transaction/root-span and log/metric byte accounting, and exposes the new reason through OnDiscardCallback.

💡 Motivation and Context

Callback failures and intentional filtering currently share the same discard reason. Distinguishing them makes client reports and local discard observers accurately describe why telemetry was dropped.

• refs: Align callback error handling with other SDKs #6081

💚 How did you test it?

• ./gradlew spotlessApply apiDump
• ./gradlew :sentry:test --tests io.sentry.SentryClientTest --tests io.sentry.clientreport.ClientReportTest
• ./gradlew :sentry:apiCheck

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

The next stack PR (#6162) marks SDK-owned event processors, followed by event processor exception handling in #6142.

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

### Fixes

- [Callback Errors 1] Report callback failures ([#6141](https://github.com/getsentry/sentry-java/pull/6141))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against 28af8f2

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.57.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[runningcode]

We should check if/how we should be logging these failures against the spec.

The spec should also clarify if non-recoverable errors should be swallowed. I don't think non-recoverable errors should be swallowed since they aren't recoverable and make it harder for customers to debug real issues.

[runningcode]

I don't know if I'm understanding the spec correctly. I see different interpretations available.

It says On failure, SDKs **MUST** emit an error-level internal log together with failure **MUST NOT** produce a billed event of any type.

Its unclear what "internal log" exactly means but isn't calling log a billable event?

Aside from being a billable event, it can also lead to failures because we have a BeforeSendLogCallback.