Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cancel biometric login overlay if authenticator is not in foreground #69

Closed
ghost opened this issue Dec 14, 2020 · 15 comments
Closed

Cancel biometric login overlay if authenticator is not in foreground #69

ghost opened this issue Dec 14, 2020 · 15 comments

Comments

@ghost
Copy link

ghost commented Dec 14, 2020

Apps using the biometric login overlay generally dismiss the overlay if the app is switched/closed.

When switching/closing Authenticator, the biometric login overlay stays in the foreground until the user taps the dead space above the biometric login request.
This makes for an awkward action when cancelling the process in comparison to what apps usually do.

@jamie-mh
Copy link
Owner

In my testing, the overlay is always cancelled when pressing the home button or switching apps.
What device are you using? It might be a bug specific the implementation of Android you are running.

@ghost
Copy link
Author

ghost commented Dec 15, 2020

OnePlus 6
LineageOS 17.1 (Android 10)

@Schokobecher
Copy link
Contributor

Schokobecher commented Dec 15, 2020

I can replicate that behavior with MIUI 12 (Android 11)

After using the on-screen task switcher key

Pressing the on-screen home key

@jamie-mh
Copy link
Owner

I've made a change that may or may not have fixed the issue. Essentially, it should cancel the prompt when the app loses focus.
It will be available in the next release. I going to keep this issue open until I can confirm that it has been fixed.

@ghost
Copy link
Author

ghost commented Dec 16, 2020

If you push a test release too me, I'd be happy to confirm prior to the official release.

@jamie-mh
Copy link
Owner

Sure, that would be great. Here's a build from the latest commit:

me.jmh.authenticatorpro-arm64-v8a.apk.zip

@ghost
Copy link
Author

ghost commented Dec 16, 2020

Sure, that would be great. Here's a build from the latest commit:

me.jmh.authenticatorpro-arm64-v8a.apk.zip

Appears to work for me.
@Schokobecher, does this fix it for you?

@Schokobecher
Copy link
Contributor

Schokobecher commented Dec 16, 2020

Just tried it, sadly it did not work.

  • Open the App
  • Instead of Unlocking hit Recents
    image
  • Instead of Unlocking hit Home
    image

Pressing above the Fingerprint section closes the app with the messageAuthentication canceled
Pressing Back closes the app with the same message

I can switch between Recents, Home and the app using the on-screen keys without the authentication prompt disappearing

@jamie-mh
Copy link
Owner

Thanks for testing it. This might be a bug in a version of a library used. Android issue 149770989. I will look into it further.

@ghost
Copy link
Author

ghost commented Dec 16, 2020

If it helps, Magisk Manager is open source on GH, and the auth functions as you'd expect it to.

@jamie-mh
Copy link
Owner

After checking the source of Magisk Manager, it doesn't seem to be doing anything different other than it doesn't allow device credentials (pin). This might have something to do with it as mentioned in the above issue. I will run some tests with the latest version of the biometrics library once it's released.

@jamie-mh
Copy link
Owner

1.14 no longer uses setDeviceCredentialAllowed(true), so this problem might be solved. If the Android bug report is accurate that is.

@ghost
Copy link
Author

ghost commented Jan 22, 2021 via email

@Schokobecher
Copy link
Contributor

Works for me, too. It's a bit awkward as the overlay lingers for half a second or so before disapperaing

@jamie-mh
Copy link
Owner

Thanks, the delay seems like normal Android behaviour, not much I can do about that. Case closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants