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.

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

iOS Passcode fallback never presented after failed TouchID #46

Closed
CAJazzer opened this issue Feb 2, 2019 · 5 comments
Closed

iOS Passcode fallback never presented after failed TouchID #46

CAJazzer opened this issue Feb 2, 2019 · 5 comments
Labels
Milestone

Comments

@CAJazzer
Copy link

CAJazzer commented Feb 2, 2019

Using the Demo app on my iOS device, the "verify with passcode fallback" call simply reverts to the catch alert() in doVerifyFingerprint() after 3 failed attempts using touch. No err is displayed (undefined), only the title and okButtonText.
my iOS version: 12.1.3

@EddyVerbruggen
Copy link
Owner

I just tested the embedded demo app on my iPad Pro and it behaves as expected: after failing to scan the finger 3 times the promise is rejected. Can you give it a try?

@CAJazzer
Copy link
Author

Thanks,

Same results.

I downloaded (cloned) the demo, then used Xcode to set a valid certificate and run the project on my iPhone 6s & on my iPad Air.

The problem is I never get the passcode screen.

Using the “verify with passcode” button, after 3 tries all I get is the alert dialog:

Biometric ID NOT
OK / canceled

Mmkay

"Never get the passcode fallback"

@marcocasadio
Copy link

hi, the same for me

@bradmartin
Copy link
Contributor

I looked into this. Might need to use the DeviceOwnerAuthentication of LAPolicy for the passcode fallback. Not 100% certain on this ATM.

@EddyVerbruggen
Copy link
Owner

I've just tested with Face ID on my iPhone X and it seems to work as expected. The only thing I can think of is this check failing so it fell through to the 'verify with custom callback' method.

So I've applied a small change where this fall through will still trigger the passcode fallback by applying the policy @bradmartin suggested.

@EddyVerbruggen EddyVerbruggen added this to the 7.0.0 milestone Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants