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

Open
opened 2025-11-26 23:16:01 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @eddiert on GitHub (Aug 27, 2025).

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.
Originally created by @eddiert on GitHub (Aug 27, 2025). ### 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 - [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.
GiteaMirror added the app:password-managerbug labels 2025-11-26 23:16:01 -06:00
Author
Owner

@bitwarden-bot commented on GitHub (Aug 27, 2025):

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

@bitwarden-bot commented on GitHub (Aug 27, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-25227
Author
Owner

@o2rhkzqx commented on GitHub (Aug 27, 2025):

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

@o2rhkzqx commented on GitHub (Aug 27, 2025): I use both Chrome and Brave and it's working fine.
Author
Owner

@eddiert commented on GitHub (Aug 29, 2025):

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

Are you visiting sites with basic auth?

@eddiert commented on GitHub (Aug 29, 2025): > I use both Chrome and Brave and it's working fine. Are you visiting sites with basic auth?
Author
Owner

@Anonym001 commented on GitHub (Aug 29, 2025):

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

@Anonym001 commented on GitHub (Aug 29, 2025): i am using microg, and currently facing this exact same issue on fennec f-droid.
Author
Owner

@eddiert commented on GitHub (Aug 30, 2025):

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

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

@eddiert commented on GitHub (Aug 30, 2025): 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. ![Image](https://github.com/user-attachments/assets/a47d3244-ddeb-445c-9508-bd0713d799b0) ![Image](https://github.com/user-attachments/assets/6eda5a44-2380-47e0-bbfe-4de9b4e75f7c) ![Image](https://github.com/user-attachments/assets/bc8ed534-29fa-4589-b9ad-a6ae378a2136) 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. ![Image](https://github.com/user-attachments/assets/099df053-e12a-43f1-b422-423a059b465b) ![Image](https://github.com/user-attachments/assets/6903ba0a-bc4a-48d5-8837-d2a244dee40f) ![Image](https://github.com/user-attachments/assets/4d9661cc-2df0-4ea6-9f9f-04895fafb222)
Author
Owner

@SaintPatrck commented on GitHub (Sep 3, 2025):

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 commented on GitHub (Sep 3, 2025): 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.
Author
Owner

@SaintPatrck commented on GitHub (Sep 26, 2025):

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.

@SaintPatrck commented on GitHub (Sep 26, 2025): 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](https://issues.chromium.org/issues/443117145).
Author
Owner

@pmr0 commented on GitHub (Nov 19, 2025):

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.

@pmr0 commented on GitHub (Nov 19, 2025): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2333