Description
The biometric authentication prompt does not appear automatically when reopening Mauth while the app is still present in the recent apps/background state. I am using a Google Pixel running GrapheneOS. When I reopen Mauth, I am shown the PIN screen with the fingerprint icon in the bottom-left corner. I have to manually tap the fingerprint icon before the Android fingerprint authentication prompt appears. This requires two actions instead of the biometric prompt appearing automatically. However, if I swipe Mauth away from the recent apps screen and then open Mauth again, the fingerprint authentication prompt appears automatically without having to tap the fingerprint icon.
Expected behavior
When biometric authentication is enabled, reopening Mauth should automatically trigger the Android biometric authentication prompt, including when Mauth is resumed from the background/recent apps.
Actual behavior
When Mauth remains in the recent apps list:
Open Mauth.
The PIN screen is displayed.
The fingerprint icon is visible in the bottom-left corner.
No biometric authentication prompt appears.
I have to tap the fingerprint icon manually.
The Android fingerprint authentication prompt then appears.
If I first swipe Mauth away from the recent apps screen and then reopen it, the biometric prompt appears automatically as expected.
Steps to reproduce
Enable PIN and biometric authentication in Mauth.
Open Mauth and authenticate.
Leave Mauth running in the background.
Reopen Mauth from the recent apps screen.
Observe that the biometric prompt does not appear automatically.
Tap the fingerprint icon in the bottom-left corner.
The fingerprint authentication prompt appears.
Swipe Mauth away from the recent apps screen.
Open Mauth again.
The biometric authentication prompt appears automatically.
Device information
Device: Google Pixel
OS: GrapheneOS
Android version: 17
Mauth version: 0.11.0
Authentication method: Fingerprint
Additional information
The fingerprint sensor and biometric authentication itself work correctly.
The issue appears to be related to when Mauth invokes the Android biometric authentication prompt. The prompt works correctly after Mauth has been removed from the recent apps list and started again.
The problem is therefore not that fingerprint authentication fails, but that the biometric prompt is not automatically triggered when the existing Mauth instance is resumed.
Description
The biometric authentication prompt does not appear automatically when reopening Mauth while the app is still present in the recent apps/background state. I am using a Google Pixel running GrapheneOS. When I reopen Mauth, I am shown the PIN screen with the fingerprint icon in the bottom-left corner. I have to manually tap the fingerprint icon before the Android fingerprint authentication prompt appears. This requires two actions instead of the biometric prompt appearing automatically. However, if I swipe Mauth away from the recent apps screen and then open Mauth again, the fingerprint authentication prompt appears automatically without having to tap the fingerprint icon.
Expected behavior
When biometric authentication is enabled, reopening Mauth should automatically trigger the Android biometric authentication prompt, including when Mauth is resumed from the background/recent apps.
Actual behavior
When Mauth remains in the recent apps list:
Open Mauth.
The PIN screen is displayed.
The fingerprint icon is visible in the bottom-left corner.
No biometric authentication prompt appears.
I have to tap the fingerprint icon manually.
The Android fingerprint authentication prompt then appears.
If I first swipe Mauth away from the recent apps screen and then reopen it, the biometric prompt appears automatically as expected.
Steps to reproduce
Enable PIN and biometric authentication in Mauth.
Open Mauth and authenticate.
Leave Mauth running in the background.
Reopen Mauth from the recent apps screen.
Observe that the biometric prompt does not appear automatically.
Tap the fingerprint icon in the bottom-left corner.
The fingerprint authentication prompt appears.
Swipe Mauth away from the recent apps screen.
Open Mauth again.
The biometric authentication prompt appears automatically.
Device information
Device: Google Pixel
OS: GrapheneOS
Android version: 17
Mauth version: 0.11.0
Authentication method: Fingerprint
Additional information
The fingerprint sensor and biometric authentication itself work correctly.
The issue appears to be related to when Mauth invokes the Android biometric authentication prompt. The prompt works correctly after Mauth has been removed from the recent apps list and started again.
The problem is therefore not that fingerprint authentication fails, but that the biometric prompt is not automatically triggered when the existing Mauth instance is resumed.