feat(android): [Logs and Metrics Enable Flags 4] Add Timber Logs opt-in

[adinauer]

PR Stack (Logs and Metrics Enable Flags)

• feat(core): Remove Logs and Metrics enable flags #5939
• feat(logback): [Logs and Metrics Enable Flags 1] Add Logs opt-in #5940
• feat(log4j2): [Logs and Metrics Enable Flags 2] Add Logs opt-in #5941
• feat(jul): [Logs and Metrics Enable Flags 3] Add Logs opt-in #5942
• feat(android): [Logs and Metrics Enable Flags 4] Add Timber Logs opt-in #5943
• feat(android): [Logs and Metrics Enable Flags 5] Add Logcat Logs opt-in #5945
• feat(spring): [Logs and Metrics Enable Flags 6] Add logging Logs opt-in for Spring Boot #5946
• feat(core): [Logs and Metrics Enable Flags 7] Remove Logs enable flag #5947
• perf(core): [Logs and Metrics Enable Flags 8] Avoid unused Logs worker thread #5952
• feat(core): [Logs and Metrics Enable Flags 9] Remove Metrics enable flag #5953
• perf(core): [Logs and Metrics Enable Flags 10] Avoid unused Metrics worker thread #5957
• fix(jul): [Logs and Metrics Enable Flags 11] Preserve null-message records #5960
• docs: [Logs and Metrics Enable Flags 12] Update options guidance #5961
• fix(android): [Logs and Metrics Enable Flags 13] Read Timber option lazily #5964
• ref(logging): [Logs and Metrics Enable Flags 14] Rename Logs opt-ins #5970

---

📜 Description

Adds a logsEnabled option to SentryTimberIntegration and SentryTimberTree, defaulting to false while preserving their existing JVM constructor signatures.

Adds SentryAndroidOptions.timberLogsEnabled and the io.sentry.timber.logs.enabled manifest key for auto-installed Timber integrations. Manually installed integrations and trees can opt in through their new constructor arguments.

Timber forwarding requires both this local opt-in and the existing aggregate core Logs flag until that flag is removed later in the stack. Event and breadcrumb capture remain unchanged.

💡 Motivation and Context

Logging integrations need explicit local opt-ins before the aggregate core Logs flag can be removed. This keeps automatic Timber log forwarding disabled by default while allowing applications to opt in through Java, Kotlin, or Android manifest configuration.

💚 How did you test it?

• ./gradlew spotlessApply apiDump
• ./gradlew :sentry-android-timber:testReleaseUnitTest :sentry-android-core:testReleaseUnitTest
• Added tests for default-disabled and explicit opt-in behavior for auto-installed and manual Timber integrations and trees
• Added regression coverage for independent event and breadcrumb capture

📝 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.

🔮 Next steps

Add the Logcat Logs opt-in before removing the aggregate core Logs flag.

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

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against f0d4297

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

[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 4f677fb. Configure here.}

[runningcode]

what do you think about naming this TimberLogCapture?

IMO, the current API isn't clear if we are outputting to Timber or capturing from Timber.

Suggested change

	public boolean isEnableTimberLogs() {
	public boolean setTimberLogCaptureEnabled() {

[lbloder]

(l) we could default to enableLogs: Boolean? = null so all old tests use the old ctor. And only the specific logging tests could set true/false.