Handle KeyStoreException in Android 8.0 #31
Conversation
This file contains 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
This exception is thrown in "verify" on Android 8.0 if new fingerprints were enrolled after "save" has been called. On Android 8.1 KeyPermanentlyInvalidatedException is thrown in the same scenario (but already in "has"), therefore I'm handling it the same - i.e. deleting the key so that it will be recreated on next call. When the application receives this error (KeyPermanentlyInvalidatedException), it should reinitialize the fingerprint usage - the user will have to reenter the password and agree to store it using the fingerprint.
|
Hello @damirarh, I don't know why your code didn't work for me, when i use .save() method error exception |
|
@SleimanB Did you check what was the |
sykaeh
pushed a commit
to ergon/cordova-plugin-keychain-touch-id
that referenced
this pull request
Sep 26, 2018
Implementation is based on sjhoeksma#31
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.
This exception is thrown in "verify" on Android 8.0 if new fingerprints were enrolled after "save" has been called. On Android 8.1 KeyPermanentlyInvalidatedException is thrown in the same scenario (but already in "has"), therefore I'm handling it the same - i.e. deleting the key so that it will be recreated on next call.
When the application receives this error (KeyPermanentlyInvalidatedException), it should reinitialize the fingerprint usage - the user will have to reenter the password and agree to store it using the fingerprint.