Fingerprint Unlock with Keyboard doesn't work

@marcfon: Thanks for getting in touch! This is the first I've heard of an issue like this, so I appreciate the details. However, can you tell me which device and version of Android you're using? I'm not able to reproduce this here. Thanks in advance!

Thanks for the update, @marcfon. Can you elaborate on the not working? Are you seeing an error message? Or are you prompted for Fingerprint Unlock from both the main app and autofill dialogue, but the fingerprint input is rejected from the main app?

Thanks @marcfon. I'd like to ask you to create a diagnostics report from your Android device:

Sending Diagnostics Reports (Android)

Attach the diagnostics to an email message addressed to support+forum@agilebits.com.

With your email please include:

• A link to this thread: https://discussions.agilebits.com/discussion/86906/fingerprint-unlock-with-keyboard-doesnt-work#latest
• Your forum username: marcfon

That way we can "connect the dots" when we see your diagnostics in our inbox.

You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here so we can track down the diagnostics and ensure that this issue is dealt with quickly. :)

Once we see the diagnostics we'll be able to better assist you. Thanks very much!

@marcfon: Thanks! I am too! I see that we've received your email, so we can continue the conversation there. We'll take a look at the diagnostics and get back to you shortly! :)

ref: KDS-67882-284

@arunsathiya: I think you may be at least partially right, especially if you're having the same issues with other apps. But if they were using their own fingerprint implementation altogether, it would have never worked in 1Password, as we're only using Google's official Nexus Imprint APIs. So I think it's more likely that they made some change in an OS update that perhaps inadvertently affected their fingerprint support. Are you also using MIUI 9.2.3.0? Do you happen to know which version you were running before?

We don't recommend using old versions, as we often include security fixes and other improvements in our updates, which is part of why they're not available. That said, if you were able to workaround the issue, great! Let us know if you need anything else.

@Timbojino: Thanks for letting us know. If you disable "Lock on Exit" in 1Password Settings > Security, does that help?

@marcfon: Not much to share. This seems to only be a problem with modified OS versions, perhaps something to do with how background and foreground processes are handled. To be clear, when you try to unlock 1Password, whether using fingerprint or your Master Password, and when opening the 1Password app or interacting with it in an overlay (as with the keyboard, or accessibility/autofill prompts), this is all just the same 1Password app; there's no difference as far as 1Password is concerned, no separate code. So when this is happening it's because something else is interfering with normal operation. We'll see if we can find a way to work around that, but we do not have control over anything outside of 1Password itself.

@marcfon: Sure. It totally worked, but wasn't nearly as flexible or powerful, and we can offer a lot more now thanks to the new tools Google has given us. The problem you're having isn't because of the overlay — we're just using Google's official autofill and accessibility APIs after all — but that whatever Xiaomi has done to the OS is breaking those. We'll see if there are ways we can work around that, but not at the expense of moving forward. With Android 9 on the horizon, custom builds of Android 6 can't be our primary focus. :(