Fingerprint login not working on Android

The same issue exists on IOS. This has been the case for many years. There is an option to enable TouchID in the client, but this has never worked for me. Beats me why that option is still in there, because I recall having asked that on these forums years ago, and the answer was that it does not work. 

I also find it hugely disappointing that this does not work properly. I mean, how hard can it be ? I have several apps that use TouchID just fine, but for some reason Unibet does not manage to properly implement it.

This the latest word in the streets as far as i know:

Didn't think that oldies goldies count as new bugs
I remember the biometric option actually had been working - for about two weeks, long time ago though.

38 minutes ago, miziel said:

Didn't think that oldies goldies count as new bugs
I remember the biometric option actually had been working - for about two weeks, long time ago though.

You are correct. I also think it worked at some time, but that has been at least 4 years ago. 

Again, what completely stumps me is that that TouchID setting is still in the app's configuration menu, yet it has not worked for years. How is that even possible ?

PS: in my activity history, I can see there were threads as old as 2019 on this subject ! Unfortunately, I cannot see the entire thread (no permission) probably because they have been archived.

It's possible we'll have it fixed within a couple of weeks. There has been work done on this recently. We're currently waiting for some legacy code to be removed, and then I'm hopeful we can make it work  

And you're all right this is an ancient issue. iOS has been worked a while ago, but Android has been broken basically forever (long before I joined the team). 

I'll be back with in update soon (hopefully)

Due to the MitID and BankID issues, this one has not seen any progress. I'm hopeful we can pick it up end of next week, when MitID and BankID fixes have hopefully been released (and proved to be working on production).

We've managed to make it work in the dev environment now. As the May release is already finalized, it might not be fixed before the June release.

We'll try and get this out end of next week. As mentioned above, May release isn't an option, so there'll be two updates to phone apps in the span of a few days.

Previously, it was only Android we had confirmed working 100%, but confirmed it for iOS today as well.