github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-12 21:24:24 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[iOS] Autofill if login only has password but no username #1328

New Issue
Closed
opened 2025-11-26 22:45:17 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 22:45:17 -06:00
Owner
Copy Link

Originally created by @xanoni on GitHub (Aug 11, 2021).

Describe the Bug

On iOS (not 100% sure if I've seen it on Android too) autofill does not work if a login only includes a password but not a username. However, there are certain apps that ask you to e.g. specify an unlock code without a username.

Bitwarden then only offers the user to "copy" the password, but it has to be manually pasted into the application.

The workaround is to just save a dummy username (e.g., "N/A"). This will make Bitwarden properly fill the password field (while ignoring the dummy username).

Steps To Reproduce

  1. Create an account for an app that prompts for only a password
  2. Leave the username empty
  3. Save and try to autofill the password when you open the app

Expected Result

Password is autofilled.

Actual Result

Bitwarden shows a "copy password" button and user has to manually paste.

Screenshots or Videos

N/A

Environment

  • Device: all iPhoens
  • Operating system: all recent iOS
  • Build Version (go to "Settings" → "About" in the app): don't currently have an iPhone available to check
  • Is this a Beta release? N

Additional Context

N/A

Originally created by @xanoni on GitHub (Aug 11, 2021). <!-- 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 On iOS (not 100% sure if I've seen it on Android too) autofill does not work if a login only includes a password but not a username. However, there are certain apps that ask you to e.g. specify an unlock code without a username. Bitwarden then only offers the user to "copy" the password, but it has to be manually pasted into the application. The workaround is to just save a dummy username (e.g., "N/A"). This will make Bitwarden properly fill the password field (while ignoring the dummy username). ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> 1. Create an account for an app that prompts for only a password 2. Leave the username empty 3. Save and try to autofill the password when you open the app ## Expected Result Password is autofilled. ## Actual Result Bitwarden shows a "copy password" button and user has to manually paste. ## Screenshots or Videos N/A ## Environment - Device: all iPhoens - Operating system: all recent iOS - Build Version (go to "Settings" → "About" in the app): don't currently have an iPhone available to check - Is this a Beta release? N ## Additional Context N/A
GiteaMirror commented 2025-11-26 22:45:17 -06:00
Author
Owner
Copy Link

@miguelarios commented on GitHub (Feb 1, 2023):

Was coming to submit this but. I don’t know if it is by design but it shouldn't. Feels the auto fill should work for username and password or just one of the other.

@miguelarios commented on GitHub (Feb 1, 2023): Was coming to submit this but. I don’t know if it is by design but it shouldn't. Feels the auto fill should work for username and password or just one of the other.
GiteaMirror commented 2025-11-26 22:45:17 -06:00
Author
Owner
Copy Link

@xanoni commented on GitHub (Feb 3, 2023):

@miguelarios Not sure if you've seen it, but try the workaround that I mentioned. I guess this is why it hasn't been fixed, yet ... easy to work around it.

The workaround is to just save a dummy username (e.g., "N/A").

@xanoni commented on GitHub (Feb 3, 2023): @miguelarios Not sure if you've seen it, but try the workaround that I mentioned. I guess this is why it hasn't been fixed, yet ... easy to work around it. > The workaround is to just save a dummy username (e.g., "N/A").
GiteaMirror commented 2025-11-26 22:45:18 -06:00
Author
Owner
Copy Link

@miguelarios commented on GitHub (Feb 3, 2023):

Hey! Yes I have done that workaround. I discovered on my own before I found the ticket. It is a nice workaround but still wanted to support your ticket as a quality of life problem 😀

@miguelarios commented on GitHub (Feb 3, 2023): Hey! Yes I have done that workaround. I discovered on my own before I found the ticket. It is a nice workaround but still wanted to support your ticket as a quality of life problem 😀
GiteaMirror commented 2025-11-26 22:45:18 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/1494

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/1494
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#1328
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?