feat(android): [Data Collection 23] Add manifest configuration

[adinauer]

PR Stack (Data Collection)

• feat(core): Data Collection #5759
• feat(core): [Data Collection 1] Add configuration types #5760
• feat(core): [Data Collection 2] Expose SentryOptions API #5761
• feat(core): [Data Collection 3] Add policy resolver #5799
• feat(graphql): [Data Collection 4] Apply GraphQL policies #5800
• feat(database): [Data Collection 5] Apply query policy #5801
• feat(spring): [Data Collection 6] Apply incoming request body policy #5802
• feat(apollo): [Data Collection 7] Apply incoming response body policy #5803
• feat(apollo): [Data Collection 8] Apply outgoing request body policy #5804
• feat(graphql): [Data Collection 9] Apply outgoing response body policy #5805
• feat(http): [Data Collection 10] Apply request header policy #5806
• feat(http): [Data Collection 11] Apply response header policy #5807
• feat(http): [Data Collection 12] Apply query parameter policy #5810
• feat(http): [Data Collection 13] Apply cookie collection policy #5811
• feat(user): [Data Collection 14] Apply user information policy #5812
• fix(android): [Data Collection 15] Scope device info cache to SDK options #5831
• test(replay): [Data Collection 16] Keep Replay independent #5832
• fix(spring): [Data Collection 18] Bind key-value policies #5834
• fix(android): [Data Collection 19] Preserve installation ID #5937
• fix(ktor): [Data Collection 20] Exclude query parameters from span descriptions #5983
• fix(opentelemetry): [Data Collection 21] Exclude queries from span descriptions #5985
• feat(core): [Data Collection 22] Add external configuration #6036
• feat(android): [Data Collection 23] Add manifest configuration #6038

---

📜 Description

Parse flattened Data Collection settings from Android manifest metadata.

Support user information, HTTP body directions, cookies, request and response headers, URL query parameters, GraphQL document and variables, and database query data. Apply only metadata fields that are present, preserving existing programmatic configuration and the unconfigured legacy state when the namespace is absent. Partial key-value settings preserve the existing mode or terms that were not specified.

Expose the internal DataCollection constructor and explicit-configuration check so Android can parse metadata into an unconfigured temporary object before merging it transactionally.

💡 Motivation and Context

Android applications commonly configure the SDK through AndroidManifest.xml. Data Collection needs equivalent manifest support without replacing settings supplied through other configuration layers or accidentally opting legacy applications into the new defaults.

Refs #5666

💚 How did you test it?

• ./gradlew :sentry:test --tests '*DataCollectionTest'
• ./gradlew :sentry-android-core:testDebugUnitTest --tests '*ManifestMetadataReaderTest'
• ./gradlew :sentry-android-core:check
• ./gradlew spotlessApply apiDump
• git diff --check

📝 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 Spring Boot binding coverage and Data Collection configuration documentation in follow-up PRs.

#skip-changelog

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

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[github-actions]

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

Generated by 🚫 dangerJS against db5a45e

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	359.30 ms	425.77 ms	66.47 ms
Size	0 B	0 B	0 B

Baseline results on branch: feat/data-collection-external-options

Startup times

Revision	Plain	With Sentry	Diff
d3db9cd	322.28 ms	378.68 ms	56.40 ms

App size

Revision	Plain	With Sentry	Diff
d3db9cd	0 B	0 B	0 B

Previous results on branch: feat/data-collection-android-manifest

Startup times

Revision	Plain	With Sentry	Diff
3dd638d	297.55 ms	374.40 ms	76.85 ms

App size

Revision	Plain	With Sentry	Diff
3dd638d	0 B	0 B	0 B

[runningcode]

hey sorry to block, but i think we need to rebase (see my note) before we can proceed with the review.

[runningcode]

weird, there's only one constructor. this makes it seem like there are two

[runningcode]

@romtsn recently refactored all the methods in this class that read from the manifest in order to allow a performance improvement from the Gradle side. PR link It looks like the changes aren't in this PR. Can you see if a rebase fixes that? Without a rebase it is likely this code would crash when run together with the Gradle plugin.