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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[expo-local-authentication] disableDeviceFallback option in android #8286

Closed
Jekiwijaya opened this issue May 13, 2020 · 4 comments
Closed

Comments

@Jekiwijaya
Copy link
Contributor

馃悰 Bug Report

I think parameter disableDeviceFallback in LocalAuthentication. authenticateAsync(options) should also set false in android

Environment

Steps to Reproduce

Expected Behavior

when passing disableDeviceFallback true in android, also disable pin fallback in android

Actual Behavior

disableDeviceFallback only supported for ios

Reproducible Demo

@LinusU
Copy link
Contributor

LinusU commented May 15, 2020

Just realised that I have already volunteered to submit a PR for this, but never got the time 馃槵

ref: #6891 (comment)

If anyone wants to pick it up, it should be pretty straight forward. When the option disableDeviceFallback is given as true, pass false to setDeviceCredentialAllowed instead of true. Please ping me if you submit a PR for this 鈽猴笍

@byCedric
Copy link
Member

Fixed by #8219 馃殌

@gie3d
Copy link

gie3d commented Jun 2, 2020

Hi @byCedric thank you very much. I'm really looking forward for that PR. Seen it's been merged but would this be release as part of the new expo version or this can be added the latest version manually? (I tried expo install expo-local-notification@9.1.1... but no luck 馃槬, it's still 9.0.0 )

Really appreciate if you could suggest

@byCedric
Copy link
Member

byCedric commented Jun 2, 2020

Hi @gie3d! You should be able to install 9.1.1, outside the expo install command 馃槃 e.g. with yarn add expo-local-authentication@9.1.1. But be aware, this only works for bare workflow projects at the moment (includes native code changes). I'm afraid this change won't make SDK 37. We are currently testing and packing SDK 38, so most of our resources go to this now. We hope to get this out soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants