[PM-25227] Android can no longer detect/fill basic auth in Chrome or Brave with new autofill settings

[eddiert]

Steps To Reproduce

Unlock Bitwarden vault
Browse to website that uses basic auth
Receive user/pass challenge
Autofill does not provide suggestions with context to the website being browsed
Clicking "Bitwarden My Vault" opens the vault and Bitwarden indicates that it is providing "Items for com.brave.browser or com.android.chrome".

Expected Result

Unlock Bitwarden vault
Go to website in browser (ex, https://www.mysite.com)
Receive user/pass challenge
Autofill suggests passwords relevant to the site (ie www.mysite.com)
Clicking on a selection fills user and pass and pressing sign-in succeeds
Clicking on "Bitwarden My Vault" would provide results based on the site being browsed

Actual Result

When accessing a website that uses basic auth, Bitwarden seems that it cannot see the web address that is being browsed for context and instead searches for items based on the browser being used (ie com.brave.browser/com.android.chrome).

Screenshots or Videos

No response

Additional Context

Edge browser on Android still works properly
Samsung Internet browser still works properly
Worked before 2025.7

Build Version

2025.7.2 (20551)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Samsung s23+
Android 15

also tested on:
Motorola Edge 2024
Android 14

Issue Tracking Info

• 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.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-25227

[eddiert]

I use both Chrome and Brave and it's working fine.

Are you visiting sites with basic auth?

[Anonym001]

i am using microg, and currently facing this exact same issue on fennec f-droid.

[eddiert]

With pictures:

Correct behavior. Unlock Bitwarden vault. Open Edge or Samsung Internet on Android. Go to https://authenticationtest.com. Click basic authentication. Correct credentials are suggested in autofill. Clicking those credentials will autofill correctly. Click Bitwarden My vault. "Items for authenticationtest.com" is shown across the top. Correct credential is suggested.

Incorrect behavior. Unlock Bitwarden vault. Open Chrome or Brave on Android. Go to https://authenticationtest.com. Click basic authentication. Incorrect credentials are suggested. No valid option to choose to autofill. Click Bitwarden My vault. "Items for com.brave.browser" is shown across the top. Incorrect credential is suggested.

[SaintPatrck]

Hi all,

Just wanted to drop in and let you know I've identified the issue and we're investigating solutions.

Unfortunately when we stopped using compatibility mode with the latest Chrome (and some Chromium variants) version to improve Autofill reliability we stopped receiving the website information during Basic Auth prompts, which is why we're falling back to the application package name that sent the Autofill request.

[SaintPatrck]

Hi all,

Popping in for an update. The Chrome team has acknowledged, confirmed, and submitted a patch to fix the issue.

More details can be found on the IssueTracker ticket.

[pmr0]

I need to roll back to the previous version, it’s really inconvenient not being able to use autofill in almost all apps that require a username and password. Autofill works fine in versions 2025.7.2 (beta) and 2025.10.1.

[Szaamaan]

Hi all,

Popping in for an update. The Chrome team has acknowledged, confirmed, and submitted a patch to fix the issue.

More details can be found on the IssueTracker ticket.

Out of curiosity... Is this a Bitwarden issue or a Chromium issue? From your reply it seems to be the latter?

It's kind of annoying as Brave is affected, and that's likely going to be slightly behind in updates compared to Chrome...

This bug isn't a showstopper (one can still find and autofill stuff, just need to find the site manually in Bitwarden), but it is fairly annoying. Especially if one accidentally presses the "autofill and save" button, which then adds a generic Brave / Chrome reference to a Bitwarden entry...

[pamperer562580892423]

@Szaamaan

Especially if one accidentally presses the "autofill and save" button, which then adds a generic Brave / Chrome reference to a Bitwarden entry...

I just read in here... And I am not so eager of testing this with an existing entry of mine, so: could you confirm if what you describe here is still happening with BW Android app 2025.11.0 (and 2025.11.1 which is rolling out at the moment) - and with enabled "autofill integration" for Brave / Chrome? (and I mean "regular autofill" - obviously this issue here about Basic auth is still unresolved...) Sorry, didn't think it through yesterday... I just tested "autofill and save" on Brave with some fake credentials (on a regular site, not basic auth) and the URI gets added as it should be (no generic Brave reference in the BW entry).

BW mobile app 2025.11.0, Brave "autofill integration" enabled, Android 15 device

[Fabio1988]

Somehow it feels to me this was already solves few weeks afterwards.. but now this bug re-appears. Again chromium which broke the bitwarden integration?

[pamperer562580892423]

I just tested this on https://authenticationtest.com with the "Basic HTTP/NTLM Authentication". And I can successfully fill the fields with the BW Android app.

But: it doesn't work with https://authenticationtest.com as a URI in the BW login item, but only with browser specific "URIs" - I tested Brave, Vivaldi and Firefox, and they needed the respective "URIs":

• Brave: com.brave.browser
• Vivaldi: com.vivaldi.browser
• Firefox: org.mozilla.firefox

(PS: If you try to autofill, the Android app does not find the matching item and presents you with the corresponding and required browser "URI" as it searches for a matching item with it.)

Sidenote: on Firefox, after filling the credentials, the login did not succeed (site loaded indefinitely) - but I guess that's a Firefox issue.

© Bitwarden Inc. 2015-2026
Version: 2026.7.1 (21803)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: abb9dde
💻 build source: bitwarden/android/actions/runs/30475765167/attempts/1
🦀 SDK: 3.0.0-7926-a9b0e184
🌩 Server: 2026.8.0 @ EU
(autofill integrations for Brave, Vivaldi and Chrome are enabled)

[Fabio1988]

Exactly same for me, previously the resolving with correct URI worked. But with browser URI it's kind of annoying if you have 4-5 basic auth website credentials stored :)