[0xadam-brown]

📜 Description

Nav3ProductsActivity, Nav3CheckoutActivity (which also covers Nav3TranslucentCheckoutActivity), and Nav3FragmentsActivity now apply the sample's configuration to the live SDK options in onCreate.

💡 Motivation and Context

Only Nav3Activity applied the sample's settings (screen tracking, user-interaction transactions and breadcrumbs) to the SDK options. The child Activities read the same configuration from their intent extras but never applied it. When Android restores the process straight into a child Activity, Nav3Activity isn't recreated, so the options stayed at the app's init defaults. Those defaults have user-interaction tracing on, so taps created ui.action.click transactions even with the toggle off.

Sample only. Split out of the Nav3 Lifecycle stack (#6480).

💚 How did you test it?

On an API 28 emulator, I turned user-interaction tracing off, opened Nav3ProductsActivity, killed the process with am kill, and restored the task. With this change, a tap made no ui.action.click transaction. Without it, it made one. That test ran on the original Nav3 Lifecycle branch, from which this change is copied unchanged. The sample compiles on top of main.

📝 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

None.

#skip-changelog

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings