fix(core): [Callback Errors 8] Report dropped profiles

[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
• feat(callbacks): [Callback Errors Optional Addon] Add opt-in strict callback mode #6173

---

📜 Description

Record one callback_error/profile loss when an attached transaction profile is dropped because beforeSendTransaction or a customer event processor throws. The same accounting path notifies OnDiscardCallback.

Pass profile presence into the private transaction-processing helpers so scope and options processors both account for the loss. Transactions without profiles do not report profile losses. SDK processor failures continue sending the transaction and attached profile without reporting a loss.

Existing transaction/span accounting, intentional-drop behavior, and catch types are unchanged. This does not change profile-file cleanup or continuous profile chunks.

💡 Motivation and Context

Transaction callback failures already record the lost transaction and spans, but omit an attached profile that is dropped with them. Include that profile so client reports and discard observers reflect the full loss.

• refs: Align callback error handling with other SDKs #6081
• Spec discussion: docs(sdk): Specify callback error isolation for user callbacks sentry-docs#19189

💚 How did you test it?

• ./gradlew spotlessApply apiDump
• ./gradlew :sentry:apiCheck :sentry:spotlessCheck :sentry:test --tests='*SentryClientTest*' --tests='*SentryClientTransactionProfileTest*' --tests='*SentryClientInternalEventProcessorTest*' --tests='*ClientReportTest*' --info — 295 tests passed
• All three attached-profile failure cases failed before the production fix and passed afterward.
• Cover scope processors, options processors, and beforeSendTransaction, each with and without an attached profile. Assert exact client-report counts and discard notifications.
• Verify SDK processor exceptions retain the attached profile and report no losses for both registration paths.

📝 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

Profile/replay artifact cleanup remains a separate follow-up. Callback-boundary catch-type changes remain deferred to the next major.

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

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

[romtsn]

one Q, LGTM otherwise

[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 8] Report dropped profiles ([#6166](https://github.com/getsentry/sentry-java/pull/6166))

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 64c1c55

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 64c1c55. Configure here.}

[cursor]

Apollo 5 skips span drop

Medium Severity

beforeSpan failures now drop the span and record callback_error in Apollo 2/3/4, OkHttp, OpenFeign, GraphQL, and Ktor, but SentryApollo5HttpInterceptor still only logs and sends the span. Apollo 5 callers keep a partially processed span and never notify OnDiscardCallback.

Additional Locations (2)

• sentry-apollo-3/src/main/java/io/sentry/apollo3/SentryApollo3HttpInterceptor.kt#L220-L235
• CHANGELOG.md#L68-L69

 

^{Reviewed by Cursor Bugbot for commit 64c1c55. Configure here.}