Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Removing Registered Fingerprints From Device Results In Unexpected Error #9

Open
SharpMobileCode opened this issue Aug 23, 2017 · 0 comments
Open

Removing Registered Fingerprints From Device Results In Unexpected Error #9

SharpMobileCode opened this issue Aug 23, 2017 · 0 comments

Comments

@SharpMobileCode
Copy link

SharpMobileCode commented Aug 23, 2017 •
edited
Loading

Description

When FingerLock is initialized after previously registered fingerprints were deleted from Android Settings produces an unexpected error. The error returned is FINGERPRINT_NOT_SUPPORTED, when it should be FINGERPRINT_REGISTRATION_NEEDED

Steps To Reproduce

  1. Register a fingerprint with device in Android settings.
  2. Calling FingerPrintManager.start() should work as expected with successful fingerprint scan.
  3. Stop the App.
  4. Go into Android Settings and remove all registered Fingerprints.
  5. Restart the App and perform a FingerprintManager.initalize()

Expected Result

onFingerLockError() should fire with FingerLockErrorState == FINGERPRINT_REGISTRATION_NEEDED

Actual Result

onFingerLockError() fires but FingerLockErrorState == FINGERPRINT_NOT_SUPPORTED
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SharpMobileCode