Hello,

I observe a strange behavior on my Samsung Note 3 while using the fingerprint feature. When I'm presented to enter my fingerprint and I decide not to deal with that at the moment for some reason (will give sample use-cases below), the next time I open the app's activity, I'm no longer presented with fingerprint challenge but asked for my master password. It bugs me that the master password isn't that easy to enter on mobile and this use-case is not rare for me to hit.

Scenario 1 (easy to reproduce): I manually lock the app from the side menu. I'm immediately presented an activity to enter my fingerprint. I obviously want to leave the app and hit "Home" button. This cause the app to fallback to master password authentication the next time I open it.

Scenario 2: When I wonder inside the app. Start creating item, discard it with a back button, the app also presents me with fingerprint screen. If I decide to ignore it and leave, I cause the master password fallback again.

Bottom line - if I don't unlock the app from fingerprint screen, I cause a fallback. And I'm obligated to do that if I don't want to write master password the next time.

Can this be fixed?

Best regards,
Antoniy

Hi @antoniy

Thanks for writing in. I would like to let you know that Full-time fingerprint is supported only on Android devices that have Android Marshmallow Fingerprint API, so if your Samsung devices with Fingerprint scanner is running Android lesser than Marshmallow, fingerprint will work just like the PIN code and you have to enter master password every time after the app is exited.

Hope this helps!

Hello @Anshu kumar

I'm running Android 6.0.1 Marshmallow, yes. And the app does not require master password when I just open it but in the specified case of not entering my fingerprint. It falls back to master password the next time I open it. It takes my decision not to swipe my finger and click a Home or Back button as an invalid fingerprint for some reason. Hope my explanation makes more sense now.

Best regards,
Antoniy

Hi @antoniy,

I would like to share that after the Marshmallow update in some Samsung's devices don't support Android fingerprint API. They use Samsung's fingerprint API, which provides ambiguous information about cancellation behaviour.

However, we are finding a workaround to solve this issue.