smsissuechecker
commented
6 years ago Hi @Qwin,
I'm the friendly issue checker. It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message. But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!
IbrahimElshafey
jor1196
So after using an iphone X I was surprised to see that most of the framework actually still works. However the problem is that the iPhone X will display after 2 attempts a dialog saying "Enter Password" (which will activate UserFallbackRequested) or Cancel (Cancelled will be activated). The problem is on the 5th try after clicking on "Enter password" it will go into user fallback however right after that I would get a dialog saying "Exceeded tries". I had hoped instead of User fallback the 5th time I would get TooManyTries so that I Can give a decent dialog back to the user that tells him he must lock and unlock his device like with fingerprint.
UPDATE: I just figured out what the issue is the TouchIDLockout has been replaced by BiometryLockout. TouchIdLockout has been deprecated. (btw the same goes for TouchIDNotAvailable and TouchIdNotEnrolled, those were replaced by biometryNotAvailable and biometryNotEnrolled). Seems that FaceID uses those LAStatus.
UPDATE 2: So I downloaded the source code and found out that it wasn't anything what I said above. The issue is just that the FACE ID process would not give an Exceeded limit status back like it does with touch id sadly. However we can maybe ask the system after it says exceeded limit, if its in that state. Currently it gives "Not available". However I am pretty sure there is a way to ask it that question.