Password with certain characters is displayed incorrectly in the Android app about mobile HOT 9 OPEN

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,

from mobile.

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.

from mobile.

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.

from mobile.

Found this one as well, the preview worked correctly in previous versions, this is a new one.

Android app verison: 2024.3.0 (9799)

from mobile.

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)

from mobile.

This is well documented but wanted to include some screenshots.

from mobile.

Closing https://github.com/bitwarden/mobile-maui/issues/3205 as duplicate

from mobile.

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!

from mobile.

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.

from mobile.