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

[GH-ISSUE #6410] [PM-31213] A suggestion to save the password that was filled in from the application #21696

New Issue
Open
opened 2026-04-16 22:16:39 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-16 22:16:39 -05:00
Owner
Copy Link

Originally created by @cyfra80 on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6410

Steps To Reproduce

In your browser, go to vault.bitwarden.eu (Chrome/Brave).

  • In the email field, select your credentials - your email will be filled in.

Click > Continue

  • In the password field, select your credentials - your password will be filled in.

Click > Logging in with your master password

You will be prompted to save your password in the Bitwarden manager (as a new entry).

Expected Result

Since the data was filled from the vault, the entry is already valid in the vault and should not be saved again.

Actual Result

There are duplicate entries in the password manager.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.12.1 (21060)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Poco X7 Pro, Xiaomi HyperOS 3.0.3.0
    • Android 16

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 @cyfra80 on GitHub (Jan 24, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6410 ### Steps To Reproduce In your browser, go to vault.bitwarden.eu (Chrome/Brave). - In the email field, select your credentials - your email will be filled in. Click > Continue - In the password field, select your credentials - your password will be filled in. Click > Logging in with your master password You will be prompted to save your password in the Bitwarden manager (as a new entry). ### Expected Result Since the data was filled from the vault, the entry is already valid in the vault and should not be saved again. ### Actual Result There are duplicate entries in the password manager. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.12.1 (21060) ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details - Poco X7 Pro, Xiaomi HyperOS 3.0.3.0 - - Android 16 ### 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 app:password-managerbug labels 2026-04-16 22:16:39 -05:00
GiteaMirror commented 2026-04-16 22:16:40 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 24, 2026):

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

<!-- gh-comment-id:3794740703 --> @bitwarden-bot commented on GitHub (Jan 24, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31213](https://bitwarden.atlassian.net/browse/PM-31213) [PM-31213]: https://bitwarden.atlassian.net/browse/PM-31213?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-16 22:16:41 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Jan 26, 2026):

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!

<!-- gh-comment-id:3797815291 --> @rmcdowell-bitwarden commented on GitHub (Jan 26, 2026): 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!
GiteaMirror commented 2026-04-16 22:16:41 -05:00
Author
Owner
Copy Link

@mc510 commented on GitHub (Apr 4, 2026):

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!

Is there, I hope, any overall effort to get Bitwarden to be less over-enthusiastic about offering to save passwords? I experience OP's issue on Windows using Firefox extension. Also Bitwarden offering to save passwords for sites where it already has a saved password, and Bitwarden offering to save passwords on fields that are not login fields. It may seem like a trivial issue that users should ignore, but it creates confusion, and there shouldn't be any confusion anywhere in the password pipeline; that's just an invitation to make a mistake.

<!-- gh-comment-id:4187742977 --> @mc510 commented on GitHub (Apr 4, 2026): > 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! Is there, I hope, any overall effort to get Bitwarden to be less over-enthusiastic about offering to save passwords? I experience OP's issue on Windows using Firefox extension. Also Bitwarden offering to save passwords for sites where it already has a saved password, and Bitwarden offering to save passwords on fields that are not login fields. It may seem like a trivial issue that users should ignore, but it creates confusion, and there shouldn't be any confusion anywhere in the password pipeline; that's just an invitation to make a mistake.
GiteaMirror commented 2026-04-16 22:16:42 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 4, 2026):

I experience OP's issue on Windows using Firefox extension.

@mc510 This issue here is about the Android app only (well, unless internally Bitwarden finds a connection to other clients too). - You probably should join this current report for the browser extensions: https://github.com/bitwarden/clients/issues/19524 (or, if you see something different, search for another matching bug report there - or open a new one yourself here: https://github.com/bitwarden/clients/issues)

<!-- gh-comment-id:4187784177 --> @pamperer562580892423 commented on GitHub (Apr 4, 2026): > I experience OP's issue on Windows using Firefox extension. @mc510 This issue here is about the Android app only (well, unless internally Bitwarden finds a connection to other clients too). - You probably should join this current report for the browser extensions: https://github.com/bitwarden/clients/issues/19524 (or, if you see something different, search for another matching bug report there - or open a new one yourself here: https://github.com/bitwarden/clients/issues)
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 app:password-manager 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#21696
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?