Closed kspearrin closed 7 years ago
Hi @kspearrin,
I'm the friendly issue checker. Thanks for using the issue template :star2: I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.
related to #53
Hmm weird.... I'm checking the availability as documented: http://img-developer.samsung.com/onlinedocs/sms/pass/com/samsung/android/sdk/pass/Spass.html#isFeatureEnabled-int-
The described behavior would mean Samsung isn't fulfilling their own API contract -.-
I double checked your devices. They seem to have a sensor. I'll just add a try/catch.
After all the edge cases I've see in Android, I'm not surprised.
Tested it on multiple Devices on mobile center. It only fails on a Galaxy Neo as in #53.
I'll fix i, soon.
Should be fixed in 1.4.5
no feedback = good feedback -> close
I'll update for our next release and let you know if I still see the issue. Thanks.
On occasion I am seeing the following crashes from older Samsung devices that I imagine don't have fingerprint available on them.
This results from doing a simple
GetAvailabilityAsync()
check.Full implementation here: https://github.com/bitwarden/mobile
Steps to reproduce
Using a SM-N930F or SM-G900A device
Use fingerprint library
Observe crash
Expected behavior
Working.
Actual behavior
UnsupportedOperationException
is thrownCrashlog
Configuration
Version of the Plugin: 1.4.4
Platform: Android 5.0 and Android 6.0.1
Device: SM-N930F, SM-G900A