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

New clone items create password history of the existing password being changed in the clone process. #2002

New Issue
Open
opened 2025-11-26 23:04:32 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 23:04:32 -06:00
Owner
Copy Link

Originally created by @shell-surfer on GitHub (Sep 10, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Create a login and add a username and password.
  2. Clone the login and edit the password before saving the cloned item.
  3. Check the password history of the cloned item to see a new password history entry of the current password that is being changed in the clone process.

Expected Result

Cloned logins do not create a password history of the current password or any hidden field that is being changed in the clone process. This is the current behaviour as seen in all other clients.

Actual Result

A new password history entry is added for the existing password that is being changed in the clone process. This usually happens only when you edit a password or a hidden field in an existing login and save it.

Screenshots or Videos

https://github.com/user-attachments/assets/6cbd5545-13a8-44a5-8bba-bf2a9d2cbfe4

https://github.com/user-attachments/assets/a94ed7e5-ab76-467e-ab39-c65d95cd6a3a

Additional Context

No response

Build Version

2024.8.1-beta (19099)

Environment Details

Device - Oneplus 9R
OS Version - Android 14

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 @shell-surfer on GitHub (Sep 10, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Create a login and add a username and password. 2. Clone the login and edit the password before saving the cloned item. 3. Check the password history of the cloned item to see a new password history entry of the current password that is being changed in the clone process. ### Expected Result Cloned logins do not create a password history of the current password or any hidden field that is being changed in the clone process. This is the current behaviour as seen in all other clients. ### Actual Result A new password history entry is added for the existing password that is being changed in the clone process. This usually happens only when you edit a password or a hidden field in an existing login and save it. ### Screenshots or Videos https://github.com/user-attachments/assets/6cbd5545-13a8-44a5-8bba-bf2a9d2cbfe4 https://github.com/user-attachments/assets/a94ed7e5-ab76-467e-ab39-c65d95cd6a3a ### Additional Context _No response_ ### Build Version 2024.8.1-beta (19099) ### Environment Details Device - Oneplus 9R OS Version - Android 14 ### 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 2025-11-26 23:04:32 -06:00
GiteaMirror commented 2025-11-26 23:04:32 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 10, 2024):

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

@bitwarden-bot commented on GitHub (Sep 10, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11932
GiteaMirror commented 2025-11-26 23:04:32 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 12, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (August 26, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

@closebot-bw commented on GitHub (Aug 12, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (August 26, 2025) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2025-11-26 23:04:33 -06:00
Author
Owner
Copy Link

@shell-surfer commented on GitHub (Aug 12, 2025):

https://github.com/bitwarden/clients/issues/14619#issuecomment-3178201585

@shell-surfer commented on GitHub (Aug 12, 2025): https://github.com/bitwarden/clients/issues/14619#issuecomment-3178201585
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#2002
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?