@ankesh-kumar
Thanks for the report. Although I don't have iOS device with face recognition, so can't verify this behavior at my end.

It will treat as code-> NotAvailable.
It should be treat with different code and should call the dialog again.

Does it mean, after tapping Don't allow, it throws `not available error ? If so, can you provide complete error log ?

should call the dialog again.

You mean it should again show the dialog ?

For example, if we deny any permission for an app by tapping don't allow, it doesn't show the dialog again right ?

@darshankawar
I am using following code:

try {
      await localAuth.authenticate(
        useErrorDialogs: true,
        biometricOnly: true,
      );
    } on PlatformException catch (e) {
      print(e.code);  **_// it is printing  "NotAvailable_**
    }

Biometric not available and Biometric is disallowed by the end-user are two complete different scenario. For both exception and message should be different. So, Developer can prompt message accordingly. Like if it is disallow , We can guide user to allow Face-Recognition from his device Settings. Hope it make sense.

Thanks for the feedback. Keeping it open and labeling for further insights from the team.

@ankesh-kumar found any solution? I'm facing the same issue.

@LouiseHsu can you try this flow on top of your flutter/plugins#6821 PR (local_auth_ios 1.0.11) and update this issue with your findings?

Hi! After debugging this issue, I've discovered that this is working correctly, as this is in line with what Apple's API is returning. if an end user disallows biometrics to be used, it is intended behaviour that the app will not be able to determine if biometrics are supported on the device, thus the "NotAvailable". Closing the issue.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.