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

starktower007 commented 2 months ago

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

Steps To Reproduce

Create a login and add a username and password.
Clone the login and edit the password before saving the cloned item.
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.