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

[GH-ISSUE #1173] When using autofill on Android, password is filled instead of username on Amazon, Google and probably some other websites #7179

New Issue
Closed
opened 2026-04-10 23:36:08 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-10 23:36:08 -05:00
Owner
Copy Link

Originally created by @Leopold702 on GitHub (Dec 11, 2020).
Original GitHub issue: https://github.com/bitwarden/android/issues/1173

Describe the Bug

I noticed that on websites that separate entering username and password into two stages (Amazon and Google are two examples of such websites) Bitwarden fills login field (that is asked on the first stage) with password

Steps To Reproduce

  1. Go to Amazon's or Google's sign in page via Google Chrome
  2. When asked for username/email trigger Bitwarden autofill
  3. Make sure that account password was inserted into username/email field

Expected Result

Username/email should be filled instead of password

Actual Result

Password is filled instead of username/email

Environment

  • Device: Google Pixel 3a
  • Operating system: Android 11
  • Build Version: 2.7.0 (3257)
  • Is this a Beta release? Y
Originally created by @Leopold702 on GitHub (Dec 11, 2020). Original GitHub issue: https://github.com/bitwarden/android/issues/1173 <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug I noticed that on websites that separate entering username and password into two stages (Amazon and Google are two examples of such websites) Bitwarden fills login field (that is asked on the first stage) with password <!-- Comment: A clear and concise description of what the bug is. --> ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> 1. Go to [Amazon's](https://www.amazon.com/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazon.com%2F%3F_encoding%3DUTF8%26ref_%3Dnavm_hdr_signin&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=anywhere_v2_us&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&) or [Google's](https://accounts.google.com/signin/v2/identifier?hl=en) sign in page via Google Chrome 2. When asked for username/email trigger Bitwarden autofill 3. Make sure that account password was inserted into username/email field ## Expected Result Username/email should be filled instead of password <!-- Comment: A clear and concise description of what you expected to happen. --> ## Actual Result Password is filled instead of username/email <!-- Comment: A clear and concise description of what is happening. --> <!-- Comment: If applicable, add screenshots and/or a short video to help explain your problem. --> ## Environment - Device: Google Pixel 3a - Operating system: Android 11 - Build Version: 2.7.0 (3257) - Is this a Beta release? Y
GiteaMirror commented 2026-04-10 23:36:11 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 12, 2020):

Hi there,

Can you please check if you encounter this behaviour on Firefox?

Thank you in advance,

<!-- gh-comment-id:743776333 --> @SergeantConfused commented on GitHub (Dec 12, 2020): Hi there, Can you please check if you encounter this behaviour on Firefox? Thank you in advance,
GiteaMirror commented 2026-04-10 23:36:11 -05:00
Author
Owner
Copy Link

@Leopold702 commented on GitHub (Dec 12, 2020):

For some reason autofill doesn't work for me at all in stable Firefox and Firefox Beta. However it worked in Firefox Nightly and fields were filled correctly on both Amazon and Google websites, so apparently problem is related specifically to Chrome. I tried in all four versions: Stable, Beta, Dev and Canary.

<!-- gh-comment-id:743781873 --> @Leopold702 commented on GitHub (Dec 12, 2020): For some reason autofill doesn't work for me at all in stable Firefox and Firefox Beta. However it worked in Firefox Nightly and fields were filled correctly on both Amazon and Google websites, so apparently problem is related specifically to Chrome. I tried in all four versions: Stable, Beta, Dev and Canary.
GiteaMirror commented 2026-04-10 23:36:12 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 12, 2020):

Thank you.

What options under 'Auto-fill Services' do you have enabled?

<!-- gh-comment-id:743793309 --> @SergeantConfused commented on GitHub (Dec 12, 2020): Thank you. What options under 'Auto-fill Services' do you have enabled?
GiteaMirror commented 2026-04-10 23:36:13 -05:00
Author
Owner
Copy Link

@Leopold702 commented on GitHub (Dec 12, 2020):

Initially I had only "Auto-fill service" and "Use Inline Autofill" enabled. After your question I tried to also enable "Use accessibility" option, but it didn't help. Problem remains when all three are enabled.

<!-- gh-comment-id:743794277 --> @Leopold702 commented on GitHub (Dec 12, 2020): Initially I had only "Auto-fill service" and "Use Inline Autofill" enabled. After your question I tried to also enable "Use accessibility" option, but it didn't help. Problem remains when all three are enabled.
GiteaMirror commented 2026-04-10 23:36:13 -05:00
Author
Owner
Copy Link

@clayadams5226 commented on GitHub (Dec 30, 2020):

Autofilling usernames only will not be possible on Android. We don't have any way of detecting a username field if it is not accompanied by a password field.

<!-- gh-comment-id:752319676 --> @clayadams5226 commented on GitHub (Dec 30, 2020): Autofilling usernames only will not be possible on Android. We don't have any way of detecting a username field if it is not accompanied by a password field.
GiteaMirror commented 2026-04-10 23:36:14 -05:00
Author
Owner
Copy Link

@Camusensei commented on GitHub (Dec 1, 2022):

I'd like to vote for re-opening this bug. At least bitwarden shouldn't fill a VISIBLE field with the password in this case. I always am horrified every time I see (any of) my password displayed anywhere (even if they are most of the time randomly generated)

<!-- gh-comment-id:1334200809 --> @Camusensei commented on GitHub (Dec 1, 2022): I'd like to vote for re-opening this bug. At least bitwarden shouldn't fill a VISIBLE field with the password in this case. I always am horrified every time I see (any of) my password displayed anywhere (even if they are most of the time randomly generated)
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#7179
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?