Fix catching authentication errors on Android 14 Pixel devices #756
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.
When encrypting values on Android 14 Pixel devices using AES_GCM it sometimes throw a different exception sometimes (I assume it is some bug in that sdk version). Here's the stack trace:
To detect it I added a recursive check on cause to find the
KeyStoreException
containingKey user not authenticated
.Tested that this works on Pixel 5 using Android 14.