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

Vault locks immediately after auto-filling #4408

Open
1 task done
antiquely8637 opened this issue Dec 3, 2024 · 4 comments
Open
1 task done

Vault locks immediately after auto-filling #4408

antiquely8637 opened this issue Dec 3, 2024 · 4 comments
Labels

Comments

@antiquely8637
Copy link

Steps To Reproduce

  1. Go to website or app to login.
  2. Unlock vault and select vault item.
  3. Refresh website.
  4. Vault locks immediately.

Expected Result

Vault stays unlocked for the duration specified in Settings.

Actual Result

Vault locks immediately after auto-filling.

Screenshots or Videos

screen-20241203-221622.mp4

Additional Context

Issue started from 2024.11.6 or 2024.11.7, was fine on 2024.11.5.
If opening and unlocking Bitwarden app from launcher, lock timeout is respected.

Build Version

2024.11.7 (19528)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Pixel 9 Pro XL on Android 15 and Pixel 5 on Android 14.

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@bitwarden-bot
Copy link

Thank you for your report! We've added this to our internal board for review.
ID: PM-15511

@fessmm
Copy link

fessmm commented Dec 3, 2024

Can confirm. Using build 2024.11.7 with Samsung S24 Ultra.

@Krychaz
Copy link
Member

Krychaz commented Dec 5, 2024

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

@larena1
Copy link

larena1 commented Dec 15, 2024

@david-livefront @lucas-livefront @vvolkgang @SaintPatrck

I see you working on lots of stuff but maybe take some time to look into this serious regression? I already reported it onemonth ago but closed it as I wasn't excatly sure under which conditions it was reproducible but so far nobody seemed to have looked into this issue here although it's been posted already 2 weeks ago? The whole process of "flagging to engineering team" doesn't really seem
to be working when big regressions like this aren't being looked into with the highest priority.

#4320

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

No branches or pull requests

5 participants