[0xadam-brown]

PR Stack (Android Nav3)

• feat(android-nav3): Android Nav3 integration #6105
• feat(android-nav3): [Android Nav3 1] Create the navigation3 module #6106
• feat(android-nav3): [Android Nav3 2] Model navigation routes #6107
• feat(android-nav3): [Android Nav3 3] Track navigation state transitions #6108
• feat(android-nav3): [Android Nav3 4] Introduce SentryNavEffect #6109

---

📜 Description

Create the new sentry-android-navigation3 module and wire it into the build.

This keeps the first step of the stack focused on the module boundary itself: Gradle registration,
module layout, and Android library scaffolding, without introducing implementation code yet.

💡 Motivation and Context

Before we can add any Nav3 behavior, we need a clean module home for it. Splitting that setup out
first makes the rest of the stack easier to review and reason about.

💚 How did you test it?

• ./gradlew :sentry-android-navigation3:assembleRelease
• ./gradlew spotlessApply
• ./gradlew apiDump

📝 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

Layer route modeling on top of the module scaffold.

#skip-changelog

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

[github-actions]

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

Generated by 🚫 dangerJS against 6c2b8f9

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings