Vault not matching correct password options on Edge for Android

S1lv3rBull3t · November 11, 2025, 12:30am

Android app not matching correct passwords for login. App trying to match all websites to com.microsoft.emmx

grb · November 11, 2025, 12:38am

If you open one of the vault items that is incorrectly being matched, enter the item edit mode, what URIs do you see stored in that login item? Is one of the stored URIs com.microsoft.emmx or anything that has the base domain com.microsoft?

Nail1684 · November 11, 2025, 1:03am

Seems to be a current bug (the GitHub issue started as being about Samsung browser, but Edge was mentioned there in the same way you described it):

github.com/bitwarden/android

[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)

opened 07:14PM - 31 Oct 25 UTC

rallyemax

bug app:password-manager

### Steps To Reproduce 1. Open ~~Samsung Internet~~ a Chromium-based browser ot…her than Chrome itself (e.g. Samsung Browser, Edge) and navigate to any login form (example: https://authenticationtest.com) 2. Tap into the username or password input field. 3. Enter the Bitwarden vault (ignore suggestions) when prompted. ### Expected Result Bitwarden should match the login item by the website’s domain (e.g., authenticationtest.com) and show entries where that domain is listed as a URI. ### Actual Result Bitwarden instead shows items only for the browser package name (for Samsung Browser, it is `androidapp://com.sec.android.app.sbrowser`) as if no website domain were available. ### Screenshots or Videos _No response_ ### Additional Context Android Autofill does provide the correct page domain to the autofill session, as confirmed by the following snippets from `logcat` and `dumpsys autofill`: > AssistStructure: Web domain: authenticationtest.com AutofillSession: Setting urlBar ... domain authenticationtest.com Login field nodes with credential hints and the URL bar node are both present in the same AssistStructure tree. Chrome’s AssistStructure has a similar “domain on one node, username/password hints on another” layout — but Chrome is matched successfully in both 2025.10.0 and 2025.10.1. Therefore the regression appears to be in Bitwarden’s association logic that maps focused credential fields to the extracted mUrlBar domain specifically in Samsung Internet’s structure. This is a domain association regression introduced in 2025.10.1, affecting Samsung Internet autofill flows. Rolling back to 2025.10.0 restores correct behavior. ### Workaround Until Bitwarden is updated with a fix, consider downgrading to version 2025.10.0, which resolves this issue completely. ### Build Version 2025.10.1 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Samsung Galaxy S25 - OS: Android 16 / OneUI 8.0 ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress. _Edited 13 Nov 2025 to include other Chromium-based browsers and emphasize the suggested workaround in its own section_

Nail1684 · November 14, 2025, 12:41pm

There is an update from a BW developer on this 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)

S1lv3rBull3t · November 14, 2025, 3:38pm

Thank you for your response

Nail1684 · November 19, 2025, 11:20pm

It seems, with Android app version 2025.11.0 there comes a fix for this bug: 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)

(I marked my post as the solution also to highlight this for everyone.)

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)

jonatan · November 28, 2025, 6:31am

Hi, I use Edge on Android. Recently, whenever a login page shows up on Edge, instead of suggesting the login associated to the page I’m currently on, it suggests Microsoft accounts. Can you check?

Nail1684 · November 28, 2025, 8:52am

@jonatan Welcome to the forum!

I moved your post into an – I think – related thread. Please check the posts here. – If you’re experiencing something different, please add more specifics (and your post can be moved back into a separate topic).

knadsady · December 18, 2025, 12:08am

FYI - Autofill compatibility mode has since been removed as of #6191 on their GitHub (which I can’t link to because I’m a new user and can’t post more than one link… sigh), which has resulted in a regression - the original problem has resurfaced! The “automatic” solution does not work and results in the same behavior before compatibility mode was introduced. I’ve submitted [PM-29915] Removal of autofill compatibility mode is a regression · Issue #6283 · bitwarden/android as a result.