fix(android): bump Auth0.Android to 3.21.1-beta.0 for Keystore2 INCOMPATIBLE_DEVICE fix - #1642
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 4 reviews per rolling hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe Android build configuration updates the Auth0 Android implementation dependency from ChangesAndroid dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized Android dependency update with no public API changes, supported by build, unit-test, and affected-device validation. No actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
…PATIBLE_DEVICE fix
a1dad4d to
7d5f09a
Compare
Changes
Bumps the bundled Auth0.Android dependency from
3.21.0to3.21.1-beta.0.That release fixes credential storage failing with
INCOMPATIBLE_DEVICEon newer Keystore2 hardware (Pixel 10, Galaxy S26, Android 16+). The RSA key used bySecureCredentialsManagerwas generated without explicitly authorizing MGF1 digests, which the newer firmware strictly enforces, so saving credentials threw on those devices. Auth0.Android now authorizes both SHA-1 and SHA-256, and treats an existing stale key's MGF1 mismatch as recoverable by deleting and regenerating it on the next login.Nothing changes in this SDK's public API — the failure surfaced here only because we delegate credential storage to Auth0.Android.
Note that
3.21.1-beta.0is a prerelease. It should be re-pinned to3.21.1once that is on Maven Central.References
Testing
:react-native-auth0:compileDebugKotlinpasses against the new version (no source changes needed).yarn buildand the existing unit tests pass.Verified on an affected device: sign in, confirm credentials persist and
getCredentials()succeeds where it previously threwINCOMPATIBLE_DEVICE.This change adds unit test coverage
This change has been tested on the latest version of the platform/language or why not
Checklist
Summary by CodeRabbit