1pw8 not needing to be unlocked to input a user and pass?

Hey @RobMendez, thanks for following up!

I noticed a fix was released a few months ago, but it sounds like you are still experiencing the same issue. Can you confirm you are on the latest version of 1Password 8 for Android?

BrendanR1P 1P_Timothy any update on fixing this bug? It's just as annoying now as it was 4 months ago. Hoping a fix is on the horizon soon. 🤞

On behalf of Brendan, you are very welcome!

BrendanR1P awesome find - thank you so much!!! I've noticed it usually times out around 30 minutes or less - very different than the 8 hours. But nonetheless, thank you for researching and duplicating the issue! 🙏👍😁🤩

Hi @RobMendez,

Thanks for your reply.

I was able to reproduce this issue on my own Android 13 device and your assumption appears to be correct from what I seen in my testing.

I opened 1Password 8 for Android, with auto-lock set to 8 hours and for master password to be required every 30 days. I then closed out of the 1Password 8 for Android app (showing as the only opened app in my Recents). I then opened my device Settings, tapped System > Developer options > Running Services > tapped the three dots in the top right and tapped Show Cached Processes.
From here I was able to see that 1Password is kept running as a cached process when the app isn't being used, but is still open in my Recents menu. If I open 1Password again from my Recents menu at this point, it opens without asking me to unlock using my account password or biometrics.

I then opened 13 random apps in a row, then checked the Show Cached Processes in Running Services in Developer Options and noticed 1Password was no longer showing as a cached or active process in Running Services. When I open 1Password 8 for Android from my Recents at this point, I am prompted to unlock the app via biometrics. Once I unlock the app, 1Password appears as a cached process again in Running Services.

To conclude, it appears the opening then closing of multiple apps at once, but leaving them in the Recents menu causes 1Password to be "pushed out" as one of the cached process, leading to the app being treated as being opened for the first time again, leading to an account password, or biometric unlock being required to activate the process again.

I've filed an issue for this with our development team to make them aware of the issue and I appreciate you for bringing it to our attention.

In terms of pinning the app. I am currently using a custom ROM and I was able to lock the 1Password for Android app in the Recents menu, by opening Recents, then tapping the lock icon below the 1Password for Android app. This prevent the issue outlined above from occurring, but I suspect this feature may be a different way of app pinning or locking added to the developers of the custom ROM I'm using, which may be why it is behaving differently than you've experienced on your device.

Apologies for the very long response, but I hope it helps. :)

-- Brendan

ref: dev/core/core#18114

1P_Timothy apologies for the late reply. It should re-open and autofill without authentication, but it doesn't.

• I usually switch focus by sliding up halfway and going back to 1Password (still in the recents). But I'm not sure if it asks me w/1Password in the recents or not. I'll have to pay closer attention and get back to you. I do know I have the settings set to password every 30 days and auto-lock after 8 hours, but I still get asked for a password (maybe after 2 weeks) and authenticate way less than 8 hours.

• When I re-open 1Password, I still have to reauth w/my fingerprint (within the 8 hours).

• I'm using a Google Pixel 6 Pro on the latest Android (OS 13, Security Oct 5, Play System Sep 1) and 1Password (8.9.3) versions.

I can't pin the app in the recents like I could on my previous OnePlus phone (Google's App Pinning seems to be an always on stuck on that app or nothing at all).

My guess is that while the app may still be shown in the recents, if I've opened a lot of other apps, maybe the OS and/or app doesn't consider itself still "open" and then requires a reauth. I'll have to test that theory (still works w/o reauth after I opened 16 other apps, so maybe it is a timing issue).

Should I send diagnostics right after it happens next time?

Happy to help @hawklet00!

@RobMendez, thanks for letting us know about this issue on your device. If 1Password is running and unlocked in the background, it should re-open or Autofill without your account password (or fingerprint).

I'd like to ask a few question to help determine the issue:
* What steps do you typically take to switch focus? Is 1Password still in your recents when you switch focus?
* If you re-open 1Password is your fingerprint required, or only for Autofill?
* What is the make and model of your device?

1P_Timothy ahh, i missed that. my apologies. thank you for your help!

1P_Timothy I actually have the opposite problem. I have fingerprint enabled and auto lock set to the maximum of 8 hours. But anytime I switch focus away and use autofill, I always have to use my fingerprint. For me, this is very annoying. I wish apps could sense that authentication was used to bypass the lock screen instead of constantly requiring re-authentication using fingerprints. It's almost as if my app is set to instantly lock, ignoring the 8-hour window. Literally, within seconds, if I switch to another app and then use autofill again I have to re-authenticate.

Hi @hawklet00, with Show filling suggestions on, you can preview your linked Logins' titles and username before selecting them to Autofill. This provides the option to quickly select and fill the right account when you might have multiple Logins for the same site. If 1Password is locked, your account password will be required to fill this information. If you prefer this information not to be previewed, you can set Show filling suggestions off.