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)