github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 19:39:41 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4475] Inline Tab Autofill Requires Unlocking Multiple Times Despite Session Timeout Settings #21360

New Issue
Closed
opened 2026-04-16 21:48:04 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 21:48:04 -05:00
Owner
Copy Link

Originally created by @o2rhkzqx on GitHub (Dec 14, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4475

Steps To Reproduce

  1. Open a website with a multi-step login process (e.g., email on the first page and password on the next page).
  2. Use the inline tab autofill to fill in the email field.
  3. Unlock the Bitwarden vault when prompted.
  4. Proceed to the next page where a password needs to be entered.
  5. Attempt to use the inline tab autofill again.

Expected Result

The vault should remain unlocked for the duration specified in the session timeout settings and not prompt for unlocking again on subsequent pages.

Actual Result

Bitwarden prompts to unlock the vault again, even though the session timeout is set to a longer duration.

Screenshots or Videos

While using the inline tab autofill feature, I encounter an issue where Bitwarden requires me to unlock multiple times, even though the session timeout is set to an option other than "Immediately." This issue only occurs when Bitwarden is locked. If Bitwarden is already unlocked, the behavior does not appear.

Additional Context

This issue only occurs when Bitwarden is locked. If Bitwarden is already unlocked, the behavior does not appear. It disrupts the user experience, especially for websites with multi-step login processes. It seems the session timeout setting is not being respected when using the inline tab autofill feature.

Build Version

Version: 2024.11.7 (19528)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: Xiomi K50i 5G
  • OS version: Android 14 (Xiomi Hyperos 1.0.6.0.ULOINXM)

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.
Originally created by @o2rhkzqx on GitHub (Dec 14, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4475 ### Steps To Reproduce 1. Open a website with a multi-step login process (e.g., email on the first page and password on the next page). 2. Use the inline tab autofill to fill in the email field. 3. Unlock the Bitwarden vault when prompted. 4. Proceed to the next page where a password needs to be entered. 5. Attempt to use the inline tab autofill again. ### Expected Result The vault should remain unlocked for the duration specified in the session timeout settings and not prompt for unlocking again on subsequent pages. ### Actual Result Bitwarden prompts to unlock the vault again, even though the session timeout is set to a longer duration. ### Screenshots or Videos While using the inline tab autofill feature, I encounter an issue where Bitwarden requires me to unlock multiple times, even though the session timeout is set to an option other than "Immediately." This issue only occurs when Bitwarden is locked. If Bitwarden is already unlocked, the behavior does not appear. ### Additional Context This issue only occurs when Bitwarden is locked. If Bitwarden is already unlocked, the behavior does not appear. It disrupts the user experience, especially for websites with multi-step login processes. It seems the session timeout setting is not being respected when using the inline tab autofill feature. ### Build Version Version: 2024.11.7 (19528) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Xiomi K50i 5G - OS version: Android 14 (Xiomi Hyperos 1.0.6.0.ULOINXM) ### Issue Tracking Info - [X] 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.
GiteaMirror added the bug label 2026-04-16 21:48:04 -05:00
GiteaMirror commented 2026-04-16 21:48:06 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 14, 2024):

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

<!-- gh-comment-id:2543137385 --> @bitwarden-bot commented on GitHub (Dec 14, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-16062
GiteaMirror commented 2026-04-16 21:48:06 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 14, 2024):

Hello @o2rhkzqx,

Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department.
Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you again,

<!-- gh-comment-id:2543172951 --> @SergeantConfused commented on GitHub (Dec 14, 2024): Hello @o2rhkzqx, Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department. Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish. Thank you again,
GiteaMirror commented 2026-04-16 21:48:06 -05:00
Author
Owner
Copy Link

@differsthecat commented on GitHub (Dec 30, 2024):

A fix for this has been merged to main, thank you!

<!-- gh-comment-id:2565806470 --> @differsthecat commented on GitHub (Dec 30, 2024): A fix for this has been merged to `main`, thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21360
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?