I recently pushed the stable version 1.3.0 of my fingerprint plugin for xamarin to NuGet. The code is available on github.
IsAvailable got replaced with
GetAvailabilityAsync() which gives you a more detailed feedback why the fingerprint authentication is not available if it isn’t available. The possible options are:
- Available: Fingerprint authentication can be used.
- NoImplementation: This plugin has no implementation for the current platform.
- NoApi: Operating system has no supported fingerprint API.
- NoPermission: App is not allowed to access the fingerprint sensor.
- NoSensor: Device has no fingerprint sensor.
- NoFingerprint: Fingerprint isn’t set up.
- Unknown: An unknown, platform specific error occurred.
If you are not interested in the reason, you can easily check the availability via
Samsung devices (even > Android 6.0) are using a own API for fingerprint authentication called Samsung Pass. The plugin supports it now. Authentication on pre Marshmallow Devices is possible, now. The used pass SDK version is 1.2.0, because 1.2.1 wasn’t working on a Lollipop device. If you are interested how I bound the obfuscated library, have a look at Samsung Binding. Tweet me if you have some better ideas.
The built in Authentication dialog on Android gives animated feedback to the user. The following example shows a failed attempt followed by requesting the fallback.
The reason text and button labels are now fully customizable. But there are some platform specific limitations.
.NET standard support
All PCLs are now targeting .NET standard 1.0. The nuget configuration has been adjusted.
Of course I fixed some bugs and did some minor improvements. If you are interested in more detail have a look at the changelog.
I could test the samsung integration only on two devices and the standard implementation only on a simulator. I’d be happy to get some feedback/bug reports/feature request from you :)