[PM-25257] Android App changes newly generated password when saved

[t-reyerf]

Steps To Reproduce

1. Go to an existing password store entry inside your vault
2. Click on Edit > Password > Generate new password
3. Let's assume the generated password is "4711"
4. Copy the password / use it for a service, e.g. PayPal
5. Press "Save" inside the password generator
6. You will be at the entry overview again
7. The password shown and stored is not 4711, but something completely different > was newly generated when clicking on "save" button
8. You are locked out of your account

Expected Result

The password shown before clicking "save" has to be the one which is saved.

Actual Result

The password shown and stored is not the one generated first, but something completely different > was again newly generated when clicking on "save" button

Screenshots or Videos

No response

Additional Context

Android version: 2025.7.2(20551)
Self hosted
Motorola Edge 50 ultra
Android 15

Build Version

2025.7.2(20551)

What server are you connecting to?

Self-host

Self-host Server Version

Latest available

Environment Details

Device: Motorola Edge 50 Ultra
OS: Android 15

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.

[bitwarden-bot]

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

[pamperer562580892423]

Self-host Server Version
Latest available

What version exactly?
And Bitwarden or Vaultwarden?

[t-reyerf]

Server-Version: 2025.5.3

Against my text from yesterday it is not the latest, my job for automatic update stopped. Shall I update and check again or keep it this way for further investigation?

We are talking about Bitwarden (not Vaultwarden).

[SaintPatrck]

Hi @t-reyerf

I'm able to reproduce what you're experiencing. The behavior mirrors that of our Browser extension, which leads me to believe it is the intended behavior. That being said, I do see valid arguments for and against this behavior. I'll bring it up to our product team for further discussion.

In the meantime, I suggest making a slight adjustment to your workflow. If you save the newly generated password or passphrase before switching apps and using it, it will not regenerate and cause the problem you're describing.

[t-reyerf]

Hello @SaintPatrck ,

thank you for your reply. I think that this behaviour has changed in one of the latest releases, since i used this workflow from day 1 and that problem has never been an issue before. Probably the behaviour of the browser extension and the desktop client has been alinged in one of the latest releases?

I personally think that the workflow to save the password before entering it into a service like PayPal is the less convenient one, because often the service declines the passwort generated e.g. because it is too long or contains chars not supported. That would mean that you have to open the entry again, edit it, adjust settings and save again before copying.

Technically this is working fine, but not so comfortable in my view.
The decision is, of course, a matter of you and your product team. Thank you in advance for the review :)