Essentials
Essentials copied to clipboard
xamarin
Biometrics API
Should this be named something different? Biometrics? We have iOS with Face ID, and presumably Android vendors will follow, so it's not really all fingerprint, however I think people mostly know this as fingerprint....
I would also say biometrics. on UWP we have Windows Hello, which could basically be anything in the world... face from my surface, fingerprint from my laptop, DNA tester from my secret bunker running Windows IoT...
Maybe we name it biometrics and in the first version we only expose fingerprint.
I just found this plugin which implement finger print reading on the 3 OS : https://github.com/smstuebe/xamarin-fingerprint
Just adding a note here.... Android is actually calling their bits 'Biometrics' now too for what used to just support Fingerprint. I think this helps validate the API naming we had in mind.
As part of this feature, for security reasons, you should also be able to detect if a new Fingerprint or FaceID has been added. Why? If you are using biometrics for authentication, and a new biometric fingerprint or face is added, the user should be required to confirm that new biometric option is valid for authentication in your app.
This will be great but it should have the following:
- Verify the fingerprint / face recognition.
- Get the fingerprint / face recognition and save in employee database for example to verify and authenticate, for example login with face recognition or fingerprint time attendance
Hi This will be a fantastic feature!! We are stuck with plugins out there that are not longer been supported and do not work when coming from the background. Basically there is not a single xamarin forms plugin that works properly including https://github.com/smstuebe/xamarin-fingerprint
Please give us the basic Biometrics for android/iOS first and build it up as you go along.
All the features other people mentioned are great but not if they have to delay the functionality for ages!!!
Great work!!!
I agree with @developer9969 the only alternative to this is xamarim-fingerprint. Would be very nice to have this feature on Xamarim.Essentials as Fingerprint is a very common thing this days.
xamarin-fingerprint is pretty broken right now. It's throwing exceptions on any device running Android 9 and any non-Samsung device running Android 8 or lower. A Java.Lang.Exception that indicates the device connected isn't a Samsung device. Even wrapping the Xamarin.Forms code in a try/catch block doesn't prevent crashes.
I 100% agree, that this now an 'Essential' feature for most apps today... Would be great to see this implemented please!
@Redth @jamesmontemagno and all the contributors THANK YOU very much for giving us Xamarin essentials. Not sure where this issue lives in the order of priority but I would really much appreciate if there is a realistic chance of being worked in the immediate future. Is this is not the case is there any chance for any of the xamarin android team to publish some guidance and advises on how to write a biometric api that uses the supported android api and I will give it a go myself.
As you guys know for sure if you write any sort of business app biometric key is a MUST. iOS is pretty straightforward in my eyes but Android is not.
many thanks
I would like to see this in Essentials. It makes sense to expose something intrinsically hardware related to Essentials. It looks like work on xamarin-fingerprint has stalled.
@jamesmontemagno can I ask if there are any plans to make this part of XE. And possibly if there is a timeline?
We do want to add this, but I think it’s safe to assume we will wait until Essentials depends directly on AndroidX and we can use the new biometric AndroidX library.
I've already done that and released a pre release package with AndroidX. Unfortunately the priorities of MS for supporting AndroidX stable, are not that high :( So I had to create the binding on my own.
https://www.nuget.org/packages/Plugin.Fingerprint/2.0.0-alpha.2
Feel free to test and give feedback: https://github.com/smstuebe/xamarin-fingerprint/issues/151
I think at this point it's safe to say that this won't be making it's way into Xamarin.Essentials anymore. Keep your eye on .NET MAUI for all new development! Thanks for all input and efforts here.
