[lazerg]

📜 Description

SentryApolloInterceptor has a new attachTracingHeaders constructor parameter. It defaults to true, so nothing changes unless you pass false. With false, the interceptor still creates spans, but it doesn't add the sentry-trace and baggage headers to the request.

The existing two-parameter primary constructor remains unchanged, preserving its Java and Kotlin binary API. A secondary constructor exposes attachTracingHeaders while retaining Kotlin usage such as SentryApolloInterceptor(attachTracingHeaders = false).

💡 Motivation and Context

In Apollo v2 the interceptor can't see the request URL, so it attaches tracing headers to every request without checking tracePropagationTargets. Before this change there was no way to turn that off. On the issue, @adinauer picked the opt-out flag.

• resolves: Add a flag to SentryApolloInterceptor to stop attaching tracing headers for Apollo v2 #5726
• resolves: JAVA-633

💚 How did you test it?

I added a test that builds the interceptor with attachTracingHeaders = false and checks that the request has no sentry-trace or baggage header. It fails without the change. ./gradlew :sentry-apollo:check passes locally.

📝 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 docs page for the Apollo integration could mention the new flag.

[lazerg]

I manually reviewed and verified each code in local before pushing

[adinauer]

Thanks for the PR @lazerg . Will take a look and maybe shuffle some things.

[adinauer]

LGTM, thank you for the contribution!