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

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