The app does not very usable on Android since UI update. Are others experiencing issues?
I’m have issues with autofill, not prompted to create or update passwords on a Galaxy S25. To either create or fill a password I have to go through a bunch of machinations of copy/paste from app to app. creating a new account on Android is not very workable any longer. Based on what I have read I have autofill setup correctly. This started on my S22 and continued when I updated to the S25. I have even tried manually adding the uri from the play store still does not work with any consistently. Are others working this hard to use the app?
1 Like
Hi @Michael_Tyson, welcome to the Bitwarden Community! 
I wish you were coming here under better circumstances, but I’ll do what I can to help! I believe that at least some of your issues may be related to this bug that was reported on Github: AutoFill Missing in Chrome and Chrome Beta · Issue #5425 · bitwarden/android · GitHub
I would recommend taking a look at the report and adding your own experiences to that thread as the team is actively investigating. If the bug I linked doesn’t quite fit, you can also open a new bug report on the same page by clicking on “New Issue.”
I hope this helps, but if you need more direct support, you can always contact Bitwarden Support directly from any Help Center | Bitwarden page. 
@Michael_Tyson … your issue also sounds similar to this GitHub issue:
Additionally, we had some similar threads here on the Forum recently - not everyone with a solution, but maybe there are some hints for you, too (or even a solution):
1 Like
I have tried the above selections. Thank you for those. But it still does not work with any consistency since the UI redo. For a lot of apps the only way to get it to work is to have mutable URI one android and one for windows. Kind of a hassle when I never had to do the before. Latest example AAA app does recognize the username field, go password field, Bitwarden vault on keybord, tap “no site information found” Search vault finds AAA, tap, select autofill and save. Auto fills password only. Addictional URI gets added for Android. Repaet process get “no site information found”
Very frustrating.
Same here, autofill has been really inconsistent since the UI update. Some apps only fill the password, not the username, and I’ve also had to deal with the copy/paste workaround. Tried resetting autofill settings and reinstalling, but no lasting fix. You’re definitely not alone in this.
Thanks all, we’ve identified an issue affecting some community members and this should be improved in the next release. Thanks for your patience!
1 Like
… do we have a certain GitHub issue or pull request to follow on that one? 
Would also be curious on the progress in fixing this. Autofill using inline and the popup overlay are really hit and miss. It seems most pronounced when I haven’t recently unlocked the vault, hitting the autofill quick tile does nothing. But then if I go unlock the vault manually, then hit the autofill tile again it will usually (like 60%) work.
I’ve also noticed the autofill overlay sometimes takes an absurdly long time, like over a full 60 seconds, to display.
Couple the above with the user hostile design trend some apps have taken where if you leave the app’s screen (like to go to your vault to copy paste your credentials) it will clear all user input every time you come back to the screen. This leaves me in the lurch where I’m locked out of apps because autofill fails and I can’t even manually copy paste my credentials over from the vault without my input being constantly erased.
I have to physically write my Wells Fargo credentials out on a piece of paper to sign in on my phone. That’s ridiculous and defeats the entire point of a password manager. Obviously Wells Fargo’s design choice is not BW’s fault but the so so performance of autofill makes it a huge PITA.
I’m on 2025.7.1 and still having lots of autofill issues.
Hi there, can you confirm where you are still having issues? Are you using the Chrome/Brave browser?
Do you have the ‘chrome autofill integration’ enabled or disabled?
Are you seeing issues with inline and overlay or just one?
Hi there, can you confirm where you are still having issues? Are you using the Chrome/Brave browser?
Most of my issues are in android apps themselves (though they may be using Chrome under the hood anyway?). Chrome has been more reliable in my experience. The last week or so my two particular pain point apps have been the Wells Fargo and U.S. Bank apps.
Do you have the ‘chrome autofill integration’ enabled or disabled?
I was not aware of the new autofill toggle for Chrome until I came across another post here mentioning it. I’ve enabled it now and will report back.
Are you seeing issues with inline and overlay or just one?
Both. Though now that I’m looking at the autofill settings in the updated app “Display autofill suggestions” seems to suggest that I have to choose either one or the other now?
It would be nice if there was an in app way to notify people about added settings like this. Until I started googling around about my issues with android 16 and BitWarden I had no idea that additional autofill settings had been added/changed.
EDIT: I’ve also been experiencing the issue reported here where even when I do get autofill options it frequently fails to actually fill anything. It takes multiple attempts before it will finally fill in fields.
Thanks for letting me know, I’m also dropping this link here for anyone else stopping by this thread: http://community.bitwarden.com/t/important-android-autofill-updates/87321/2
That appears to be a bad link.
Still having issues even with the new chrome autofill option toggled on. Inline autofill still doesn’t work in the U.S. Bank app. It took three attempts using the autofill quick settings tile to finally get it to fill in the credentials. First time it told me no fields were found. Second time it found them, I clicked the vault entry, the vault disappeared and my credentials were not filled. Third attempt it finally worked.
Wells Fargo app worked once with inline autofill. Closed the app and re-opened it and now it’s not presenting inline autofill choices it had just moments ago. Same deal with the autofill tile, it takes multiple attempts to get it to 1) find fields 2) to actually put your credentials in said fields. Seems to work better if you first unlock the vault before attempting auto fill which IMO shouldn’t be necessary.
I’ve already followed the tips on troubleshooting autofill issues including disabling and re-enabling the services as outlined here: Troubleshoot Android Autofill | Bitwarden
Page should work now 
Did those pages work previously? Or did they always cause an issue?
For anything beyond the scope of the link you mentioned, you can report specific autofill issues here, or alternatively file a bug report, or open a support ticket so the team can investigate further.
There are also instructions here, on how to temporarily share non-sensitive information with the team using Flight Recorder.
They worked well at one point, before the ground up app redesign. Maybe on Android 14 or 15? Android 16 upgrade made things markedly worse all around for autofill.
To summarize my two main issues are the inline autofill in gboard doesn’t show like 75% of the time and I have to use the autofill tile in quick settings. Related to my forced use of the autofill tile i often have to use the tile multiple times as it either claims to not detect fillable fields or it detects them and then flat out fails to put anything in the fields (or it will fill one field and not the other). Some apps are better than others but it’s difficult to tell what parts of these issues are down to app design vs bitwarden vs android. Whether or not the vault is already unlocked seems to also play a role in whether or not autofill options are presented and how well they work.
I can open github issues but it looks like all of the issues I’m having are already talked about in other github issues/forum threads. I don’t want to create additional work for the devs by opening duplicate threads for issues that have already been mentioned elsewhere by users.
Thanks for confirmation. If you do sumbit a ticket, here is how to temporarily enable Flight Recorder to provide non-sensitive information to the support team for further review.
Hi same here on two mobile Android 15 phone
S25 Samsung and pixel 9a
@cddu33 Welcome to the forum!
Just to understand it better: are you already on the mobile app version 2025.7.0 / .7.1 and followed these new instructions: Important Android Autofill Updates – and still see… well, what exactly? “Same here” is always a bit hard to interpret 
, so please elaborate if your issues persist despite those new updates…