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
LocalAuthentication does not match UX of other Android Apps in SDK37 #8246
Comments
Any news on this? Its not something urgent, but we are thinking about implementing this at my company, would be nice to have this working |
Seems like this is potentially an issue with Google blacklisting some of the major Samsung flagships. However there must be a solution as every Native app I use on the S10+ can display the Biometric Popup correctly. |
Hi, I am having the same issue with Samsung device, @ConorWatsonSoar did you find any solution for this issue? |
Hey @ConorWatsonSoar @KiratiBhuva any updates on this ? |
This issue is stale because it has been open for 60 days with no activity. If there is no activity in the next 7 days, the issue will be closed. |
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem. |
馃悰 Bug Report
Environment
Targeting Android via Standalone and Client. Reproduced on a Samsung Galaxy S10+, with the latest version of the Expo Client installed (v2.15.0).
Steps to Reproduce
LocalAuthentication.authenticateAsync()
Expected Behavior
Android Authentication UI should appear on top of the screen that is currently requests Authentication.
Actual Behavior
Android Authentication UI appears in a separate screen before the user is navigated back to their original screen.
Reproducible Demo
I have created a reproducible Snack demo here. I can also confirm that this problem is exhibited when a standalone app has been built in SDK37.
Interestingly, the UI appears correctly when using the Android simulator on the Snack. However running the Snack on my Samsung S10+ I can reproduce the unexpected behaviour, and my friend is also able to reproduce similar behaviour on his One Plus 7 Pro.
EDIT: I managed to get a hold of a Pixel 4, and the UI does appear correctly on this device. It's possible it's a "Custom" UI issue?
The text was updated successfully, but these errors were encountered: