github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-11 02:15:43 -05:00
Code Issues 1.1k Packages Projects Releases 124 Wiki Activity

Credentials aren't entered and auto-fill overlay doesn't appear after unlocking vault #1279

New Issue
Closed
opened 2025-11-26 22:43:33 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 22:43:33 -06:00
Owner
Copy Link

Originally created by @ikt32 on GitHub (Apr 20, 2021).

Describe the Bug

The auto-fill overlay does not appear after unlocking the vault. A page refresh is needed to have the auto-fill service overlay appear again.

Steps To Reproduce

  1. Lock the vault.
  2. Go to any page with a login.
  3. Tap on one of the fields. The "Auto-fill with Bitwarden / Vault is locked" overlay appears.
  4. Tap on the overlay and unlock the vault by either password or biometrics.
  5. (Optional?) Tap on the found login credentials inside the Bitwarden app.
  6. The Bitwarden app returns to the browser. No credentials are actually entered.
  7. Tap again on one of the fields. No overlay appears.
  8. Refresh the page.
  9. Tap on the fields again. The overlay finally appears, and a login can be selected.

Expected Result

In step 6, I would expect the login credentials to have been entered after the Bitwarden app returns.

If not possible, I would expect the auto-fill overlay to appear when tapping one of the fields.

Actual Result

After authenticating and selecting a set of login credentials, none are actually entered.

When returned to the login page, no auto-fill overlay appears when tapping on one of the fields.

A refresh of the page is required to get the auto-fill overlay to appear when tapping on one of the fields.

Screenshots or Videos

Video on YouTube

The recording is censored by Android during steps 4 -> 5 -> 6.

Environment

  • Device: Google Pixel 4a 5G
  • Operating system: Android 11
  • Build Version: 2.9.1 (3444)
  • Is this a Beta release? No

Additional Context

  • Browser: Firefox Nightly, latest version (Nightly 210417 17:00, build #2015805195)

Has happened ever since I switched from Lockwise to Bitwarden though, Lockwise did not have this specific issue.

Originally created by @ikt32 on GitHub (Apr 20, 2021). ## Describe the Bug The auto-fill overlay does not appear after unlocking the vault. A page refresh is needed to have the auto-fill service overlay appear again. ## Steps To Reproduce 1. Lock the vault. 2. Go to any page with a login. 3. Tap on one of the fields. The "Auto-fill with Bitwarden / Vault is locked" overlay appears. 4. Tap on the overlay and unlock the vault by either password or biometrics. 5. (Optional?) Tap on the found login credentials inside the Bitwarden app. 6. The Bitwarden app returns to the browser. No credentials are actually entered. 7. Tap again on one of the fields. No overlay appears. 8. Refresh the page. 9. Tap on the fields again. The overlay finally appears, and a login can be selected. ## Expected Result In step 6, I would expect the login credentials to have been entered after the Bitwarden app returns. If not possible, I would expect the auto-fill overlay to appear when tapping one of the fields. ## Actual Result After authenticating and selecting a set of login credentials, none are actually entered. When returned to the login page, no auto-fill overlay appears when tapping on one of the fields. A refresh of the page is required to get the auto-fill overlay to appear when tapping on one of the fields. ## Screenshots or Videos [Video on YouTube](https://www.youtube.com/watch?v=pKH7WFNaSpU) The recording is censored by Android during steps 4 -> 5 -> 6. ## Environment - Device: Google Pixel 4a 5G - Operating system: Android 11 - Build Version: 2.9.1 (3444) - Is this a Beta release? No ## Additional Context - Browser: Firefox Nightly, latest version (Nightly 210417 17:00, build #2015805195) Has happened ever since I switched from Lockwise to Bitwarden though, Lockwise did not have this specific issue.
GiteaMirror commented 2025-11-26 22:43:34 -06:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Apr 29, 2021):

Thanks for reporting this issue. This is a known problem that affects a number of sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.

@eliykat commented on GitHub (Apr 29, 2021): Thanks for reporting this issue. This is a known problem that affects a number of sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.
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
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#1279
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?