bitwarden
Password with certain characters is displayed incorrectly in the Android app
Steps To Reproduce
- Create a login with password that ends with characters
<M. - View the login's password in the Android app. The two characters are rendered only as
M. The only clue that something is wrong is that M is displayed in the orange color as if it's a special character. - Edit the login entry and view the password.
- It's displayed correctly as
<M.
Expected Result
Password must be displayed correctly.
Actual Result
Password is displayed incorrectly. Unsuspecting users would enter wrong passwords and face various problems.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Android
Operating System Version
12
Device
Samsung Galaxy M31s
Build Version
2024.3.0
Beta
- [ ] Using a pre-release version of the application.
Hi @rabindra-harlalka,
Thank you for your report. I was able to reproduce this behaviour and I have flagged it to our Engineering team.
If you wish to add any further information, such as screenshots or screen recordings, please feel free to do so at any time - our Engineering team will be happy to review them.
Thank you again,
If you use some special characters like _ or * after a <, those characters will not be displayed either.
It seems, that > is an active character, too.
So the password a<_<1<*<m<><%>q will be displayed as a1mq.
All characters of the passwordwill be shown in edit mode, though.
I have also encountered this bug. I am unable to share a screenshot as the app prevents but I can confirm that I am seeing this same bug in version: 2024.3.0 (9799)
Found this one as well, the preview worked correctly in previous versions, this is a new one.
Android app verison: 2024.3.0 (9799)
This is well documented but wanted to include some screenshots.
Closing https://github.com/bitwarden/mobile-maui/issues/3205 as duplicate
Good, a bug report for this already exists. It almost drove me crazy entering a password exactly as it was displayed and it was not being accepted, because it tas displayed wrong. I had to copy and paste elsewhere to view the password and realise what was happening.
Just logged some info on #3256 before I found this bug. This one's more similar to what I'm experiencing.
One other thing I noted is that copy/paste contains the full password, so it's only displaying incorrectly, thankfully minimising the impact!
Just to add more fuel to this fire, I wanted to say that I also am experiencing this issue. This is a not-insignificant defect, since sometimes:
- auto-fill doesn't work
- you can't paste into the password field
And so, you have to look at the password and pain-fill the field.
Any clue as to when this will be resolved? The issue was opened three months ago, and was reported to the engineering team a day after opening.
Hello,
Please try reproducing the issue with the beta version of the native app. The beta program can be joined, and the app downloaded from here: https://community.bitwarden.com/t/about-the-beta-program/39185
Recent updates have been made in the beta builds, so it would be helpful to check if the issue still occurs with the latest version.
Thank you for your cooperation, and looking forward to the feedback!
Hello,
Please try reproducing the issue with the beta version of the native app. The beta program can be joined, and the app downloaded from here: https://community.bitwarden.com/t/about-the-beta-program/39185
Recent updates have been made in the beta builds, so it would be helpful to check if the issue still occurs with the latest version.
Thank you for your cooperation, and looking forward to the feedback!
I eventually landed here after discovering this same issue. I just downloaded and installed v2024.8.0 (18985) and the issue appears to be resolved in that version.
That's great to know @nbros652, that has been my experience as well.
I will leave this issue open a couple more days just in case.
I didn't download the beta like @nbros652 but I did update to 2024.10.0 based on the comment about the beta 2024.8.0 version. I still have the issue on 2024.10.0, so I had to roll back again
Any update here? Haven't seen a new release so I assume this is still broken.
