feat(oidc_android,oidc_ios)!: first-party native auth, drop flutter_appauth [WIP]

[ahmednfwela]

Implements the native authorization / end-session browser flow directly in the existing platform packages (no shared mixin, no new package, per maintainer direction), replacing flutter_appauth with first-party code. All OIDC logic (URL building, PKCE, state, nonce, response parsing) stays in pure-Dart oidc_core (request.generateUri() + OidcEndpoints.parseAuthorizeResponse()), so PKCE/state/nonce are identical on every platform.

Status

• ✅ Android (oidc_android): OidcAndroid implements OidcPlatform directly; native OidcPlugin.kt uses Chrome Custom Tabs (androidx.browser:browser:1.10.0) + redirect capture + cancellation; flutter_appauth/oidc_flutter_appauth deps removed; README documents the redirect intent-filter. Dart verified: analyze clean, 5/5 mock-channel tests.
• ⏳ iOS (oidc_ios): in progress — ASWebAuthenticationSession.
• ⏳ macOS: shares the Apple code (follow-up).
• ⏳ Example-app manifests (Android intent-filter / iOS URL scheme) for integration E2E.

Not verifiable locally (needs this CI / a device)

Native Kotlin/Swift compilation and on-device E2E — that is exactly what the draft CI run will exercise. Expect the native integration jobs to be the iteration surface.

Roadmap: #205 (remove flutter_appauth). De-risks #76, #118, #128, #130, #174, #213, #281, #309.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 227457b7-3193-4fb6-aab7-77d910d9e60c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/native-channel-auth

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gitguardian]

⚠️ GitGuardian has uncovered 9 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8133728	Triggered	Elliptic Curve Private Key	c3a364b	packages/x509_plus/test/files/ec256.key	View secret
8133786	Triggered	Generic Private Key	c3a364b	packages/jose_plus/test/pem/rsa.key	View secret
8133732	Triggered	Elliptic Curve Private Key	c3a364b	packages/x509_plus/test/files/ec256k.key	View secret
8133787	Triggered	Elliptic Curve Private Key	c3a364b	packages/jose_plus/test/pem/ec256k.key	View secret
8133729	Triggered	Elliptic Curve Private Key	c3a364b	packages/x509_plus/test/files/ec521.private.key	View secret
8133726	Triggered	Elliptic Curve Private Key	c3a364b	packages/x509_plus/test/files/ec384.private.key	View secret
8133785	Triggered	Elliptic Curve Private Key	c3a364b	packages/jose_plus/test/pem/ec256.key	View secret
8133784	Triggered	RSA Private Key	c3a364b	packages/jose_plus/example/jwtRS512.key	View secret
8133733	Triggered	Elliptic Curve Private Key	c3a364b	packages/x509_plus/test/files/ec384.key	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[github-actions]

Visit the preview URL for this PR (updated for commit f158c4e):

https://oidc-flutter-docs--pr-315-docs-pk5pwocy.web.app

_{(expires Sat, 06 Jun 2026 03:23:24 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: be73cc36b5cf3e9d187cedf949ae5b2218b855cd}

[github-actions]

Visit the preview URL for this PR (updated for commit f158c4e):

https://oidc-flutter-example--pr-315-example-zu4669ju.web.app

_{(expires Sat, 06 Jun 2026 03:23:34 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 5ca8b925ef0acd3a0c8fced26fcc6d1bfac11b49}