feat(android-nav3): [Android Nav3 5] Make SentryNavEffect accessible to sample apps

[0xadam-brown]

PR Stack (Android Nav3)

• feat(android-nav3): Android Nav3 integration #6128
• feat(android-nav3): [Android Nav3 1] Create the navigation3 module #6129
• feat(android-nav3): [Android Nav3 2] Model navigation routes #6130
• feat(android-nav3): [Android Nav3 3] Track navigation state transitions #6131
• feat(android-nav3): [Android Nav3 4] Introduce SentryNavEffect #6132
• feat(android-nav3): [Android Nav3 5] Make SentryNavEffect accessible to sample apps #6137

---

📜 Description

Make SentryNavEffect public so the Nav3 sample app can consume the API shape we intend to expose.

Still marked as @ApiStatus.Internal until we actually release + include a CHANGELOG.

💡 Motivation and Context

The sample app should validate the actual API host apps will use. Keeping SentryNavEffect
internal blocks that validation, so this PR exposes the effect as the next step in the Nav3 stack.

addresses: JAVA-274

💚 How did you test it?

• Existing unit tests
• API dump updated via CI / local verification as needed

📝 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.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

• Expose the remaining Nav3 public APIs needed by the sample app
• Add module README and docs

#skip-changelog

⚠️ Merge this PR using a merge commit (not squash). This PR should merge into the effect branch first, then flow back down the chain.

[github-actions]

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

Generated by 🚫 dangerJS against 323c163

[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.}

^{Reviewed by Cursor Bugbot for commit 323c163. Configure here.}

[cursor]

Contradictory public API status annotations

Low Severity

SentryNavEffect and its parameter types are annotated with both @ApiStatus.Experimental and @ApiStatus.Internal. Those markers conflict: Internal means the API is not for host apps, while Experimental means it is public but unstable. The PR presents this as the integration surface host apps will use.

Additional Locations (2)

• sentry-android-navigation3/src/main/kotlin/io/sentry/compose/navigation3/RouteExtractors.kt#L48-L52
• sentry-android-navigation3/src/main/kotlin/io/sentry/compose/navigation3/SentryNavOptions.kt#L20-L24

 

^{Triggered by project rule: PR Review Guidelines for Cursor Bugbot}

^{Reviewed by Cursor Bugbot for commit 323c163. Configure here.}

[0xadam-brown]

Not sure what our convention here is, and happy to conform as needed.

This PR is meant to make SentryNavEffect public exclusively for our sample apps; official publication will come later, accompanied by a CHANGELOG entry, etc., at which point these APIs will still be experimental.

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings