Yep the autofill flag definitely helps in Chrome, not so much in apps (IME so far at least).
@dwbit have just sent through another Flight Recorder log - this time happening reproducibly on 192.168.8.1 (GL-iNET web interface) on Chrome for Android. This used to work fine a few months ago and is definitely having issues now with it never autofilling and coming up with the error of no password fields detected when trying to trigger it to fill (works fine on desktop Chrome for Windows).
1 Like
There seems to be a new issue with autofilling in Edge on Android. Bitwarden doesn’t recognize it as a browser any more. For any password, it’s offering “Items for com.microsoft.emmx” and showing Microsoft accounts rather than for the page the browser is on.
1 Like
@alanh The team is working on a fix for that issue, stay tuned!
1 Like
Seems that for the moment, Chrome, Brave and Firefox are unaffected by this current bug – comment from a BW developer in the corresponding GitHub issue:
(direct link to that comment: [PM-27708] Autofill regression in multiple browsers: Bitwarden 2025.10.1 stops matching by website domain and falls back to package name (e.g. com.sec.android.app.sbrowser) · Issue #6107 · bitwarden/android · GitHub)
It seems, with Android app version 2025.11.0 there comes a fix for this previously mentioned bug: [PM-27708] Autofill regression in multiple browsers: Bitwarden 2025.10.1 stops matching by website domain and falls back to package name (e.g. com.sec.android.app.sbrowser) · Issue #6107 · bitwarden/android · GitHub → a new Compatibility Mode for the affected browsers.
Here is a new Help Site entry for that Compatiblity Mode: [Edit: I removed the link now, as that Help Site section was removed now also – see the Update below] (essentially: if using Edge, Samsung Internet, Opera, then check Settings → Autofill → Use compatibility mode for browser autofill)
Update:
It seems, the new compatibility mode is only a temporary thing… Another “automatic” solution gets implemented and the compatibility mode will be removed with one of the next releases. (–> 🍒 PM-28545: Remove the compatibility mode toggle from the Autofill screen by SaintPatrck · Pull Request #6191 · bitwarden/android · GitHub)
1 Like
Thanks for flagging - looks like if using Chrome it changing the option won’t make a difference (“Chrome, Brave, and Firefox will always use the standard autofill logic regardless of this option, ensuring you are maximally protected.“) - do we know if the `#autofill-update-context-for-web-contents` flag is still required? Some of the issue I have aren’t in Chrome itself but filling in login details in apps so I’m not sure that makes much difference anyway.
Not quite an auto fill issue, sorry, but with Passkeys (I see an Bitwarden employee has been in this particular thread). Was trying to join the forums here, and tried signing up with my Google account. I have a passkey saved in my Bitwarden for my Google account (Android 16, Google Pixel 7 Pro, Google Chrome as my browser), but when signing up with my Google account it wanted me to verify, and should have brought up a prompt for me to use my saved passkey. Instead, I get what’s in the image below. Please help! I’d really like to not get locked out of my Google account if it ever prompted me to verify at a time when I actually really needed it.
@Historygeek1945 Welcome to the forum!
I think what you describe is more or less the same as it was reported here: Logging into Android itself with Google Account fails to load passkey from Bitwarden · Issue #5506 · bitwarden/android · GitHub
A post was split to a new topic: Autofill doesn’t work – Vivaldi browser (Android)
I am so close to forking this app just to remove the Autofill nag that pops up EVERY SINGLE TIME I OPEN THE APP. Every single time I’m in the middle of something I open this app and it pops up this god awful stupid useless reminder about Autofill. I’m going to rip my hair out.
And today there was ANOTHER DIFFERENT kind of popup about autofill, in the middle of me doing something. Just offensively horrible zero-thought UX.
@colemickens Welcome to the forum!
I’m curious – what is your use case for installing the Android mobile app, but not enabling autofill and/or not enabling the autofill integrations for Chrome and Brave?
Sadly I’m still having issues with intermittent autofill on Android for M365 logins. I’ve filled out the webform multiple times and also sent over flight recorder logs but no change despite a number of updates - is there any timescale for a fix?
- which exact URL?
- which browser? (including the browser version)
- what Android app version?
- username/password login or passkey login?
This is for the Microsoft 365 logins on Android (e.g., Outlook, Teams). Not in the browser. I’m on the latest version (2026.1.0) but it has been like this since first raised a few months ago.
The M365 process is standard - when reauthenticating don’t need to re-enter username, just password then TOTP. It used to work flawlessly and reliably but with the changes to the app late last year it is now only successful part of the time. Often you tap on the relevant login and no password is filled out and have to manually load BW separately and copy and paste it, then the TOTP. When it works well then you paste password, go next and then paste TOTP. I’ve recorded numerous flight recorder logs for this as requested and not had any update.
Like many I have multiple M365 accounts on my phone and have to reauthenticate most of them weekly so it’s frustrating to have to keep manually copying and pasting, especially when it does sometimes work!
Update for Vivaldi mobile browser
Since the latest update of Vivaldi (version 7.8), you have to enable the following in the Vivaldi settings for it to continue to work with the Bitwarden app: go to “Autofill services”, enable “Autofill using another service” there and allow Vivaldi to restart.
(this seems to work – for now?! – without enabling “autofill integration” for Vivaldi in the BW mobile app, which not even is there as an option at the moment…)
UPDATE: As of Android app 2026.2.1, the “autofill integration” for Vivaldi can be enabled via the the BW app itself (Settings → Autofill), like it worked for Chrome and Brave before:
1 Like