Skip to content

Removing Registered Fingerprints From Device Results In Unexpected Error #9

@SharpMobileCode

Description

@SharpMobileCode

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions