Repository navigation
fix(android): bump Auth0.Android to 4.2.1 to keep users logged in after upgrade - #1708
Merged
Merged
Conversation
|
Caution Review failedThe pull request is closed. 📝 Summary
Merge Risk:
|
pmathew92
approved these changes
Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps Auth0.Android from 4.1.0 to 4.2.1 and updates the version in the migration guide.
Apps that upgrade from react-native-auth0 5.4.0 or older (Auth0.Android 3.12.x and earlier) lose their stored session on the first launch.
getCredentials()rejects withCRYPTO_EXCEPTIONand the saved credentials are deleted.The cause was in Auth0.Android 4.1.0 and 4.2.0. When the old PKCS1 RSA key rejected the OAEP cipher, the decrypt step deleted the RSA and AES keys before the PKCS1 migration could run, so there was nothing left to migrate. 4.2.1 (auth0/Auth0.Android#1110) stops deleting the keys there and lets the migration run first. Keys that fail the migration are still regenerated as before.
The same fix shipped for v5 in #1706.