Bug when unlocking via fingerprint sensor

[fallsdevil]

Always when you open the app on the first try, it closes unexpectedly and shows a message written "fingerprint operation canceled".

To Reproduce
Steps to reproduce the behavior:

1. open the app
2. position my fingerprint, seconds later
3. the application closes
4. pop-up with error message

Expected behavior
That the app unlocked normally on the first attempt, and not just on the second after the strange error on the first time.

App Version
1.22.0

Additional context
Image with the error message, it is in Portuguese as it is my device language. Also, I downloaded the app from the Play Store

[HigH-HawK]

Hey @fallsdevil

Can you please add your device info (phone / tablet make/model and android version)

Might make it easier to reproduce and find the error

[fallsdevil]

Of course, I was using the Motorola Moto E22 smartphone running Android 12.
I'm currently using the Galaxy A10s Android 11 which has the same bug.

[HigH-HawK]

It seems that someone else has the same issue in #851 (at the end)

[fallsdevil]

I upgraded to the latest version of the play store and it's having the same problem, so the solution would be to disable the digital sensor unlock?

[jamie-mh]

I am not able to reproduce this on any of my devices or the emulator. You probably have an app on your device that interferes with the fingerprint scanning. Do you have an app that uses an accessibility service such as a password manager for instance installed?

Thanks

[fallsdevil]

Yes, I use bitwarden and maybe macrodroid has access to this accessibility, I will try to remove it to test.

[fallsdevil]

I disabled all applications with this accessibility and now the app no longer opens, it always closes a few seconds after opening every time...

[ouzowtf]

I have the same problem on my Pixel 4a 5G with Android 14 since a few months.
It works normally on the second try, but always produces the described error message on the first try.

[NebularNerd]

It seems to be a weird glitch that cannot be traced (see #851), both myself and @jamie-mh have Samsung S22's, mine demonstrates the bug (and it did on a previous phone), Jamie's does not.

As suggested before, maybe a debug version that outputs its own logs might help.