fix(integrations): [Callback Errors 9] Guard custom callbacks

[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

Guard the remaining custom capture and span callbacks covered by this change:

• Android screenshot and view hierarchy: log callback exceptions, skip attachment capture, and retain the error event.
• OkHttp, OpenFeign, GraphQL (both integration versions), and Ktor: catch beforeSpan exceptions and drop the affected span without disrupting the request or replacing its original exception.
• Apollo legacy/3/4: change existing exception handlers to drop the span instead of retaining it.

Failed spans still finish, including OkHttp event-listener cleanup. Normal callback return values, intentional drops, and existing catch types remain unchanged. New guards catch Exception; the broader catch-type sweep remains separate. No public API changes.

💡 Motivation and Context

Custom filtering callbacks must not cause requests to fail or allow potentially partially processed telemetry to be sent. Android callbacks decide whether to capture an attachment, so their failure skips that capture rather than dropping the error event.

• 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?

• Verified 18 regression cases fail before the production fix and pass afterward.
• 454 tests passed across the OkHttp, OpenFeign, GraphQL core/17/22, Ktor, and Apollo legacy/3/4 suites, plus the Android screenshot and view-hierarchy processor suites.
• Cover response preservation, original request exceptions, partial span mutations, synchronous/asynchronous GraphQL results, logging, span completion, breadcrumbs, and subsequent successful Android captures.
• Corrected two test-fixture gaps: Ktor was not installing the supplied beforeSpan callback; the screenshot allow-capture test was setting the view-hierarchy callback.
• ./gradlew spotlessApply apiDump and apiCheck passed; no API files changed.

📝 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 and remaining scope/feedback callbacks are separate follow-ups. Existing Throwable callback-boundary handling remains 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]

My clanker found a couple of more callbacks, not sure if we want to factor them in?

• Spring SentryUserProvider.provideUser in SentryUserFilter
• TransactionNameProvider in SentryRequestHttpServletRequestProcessor
• SentryTracingFilter
• OnOversizedEventCallback
• BeforeEnvelopeCallback
• OnDiscardCallback

[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 9] Guard custom callbacks ([#6167](https://github.com/getsentry/sentry-java/pull/6167))

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 e87fddf