github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-10 00:28:29 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

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

New Issue
Open
opened 2026-04-23 18:04:12 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-23 18:04:12 -05:00
Owner
Copy Link

Originally created by @eddiert on GitHub (Aug 27, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5789

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). Original GitHub issue: https://github.com/bitwarden/android/issues/5789 ### 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 bugapp:password-manager labels 2026-04-23 18:04:12 -05:00
GiteaMirror commented 2026-04-23 18:04:14 -05:00
Author
Owner
Copy Link

@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

<!-- gh-comment-id:3226735106 --> @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
GiteaMirror commented 2026-04-23 18:04:15 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:3228768183 --> @o2rhkzqx commented on GitHub (Aug 27, 2025): I use both Chrome and Brave and it's working fine.
GiteaMirror commented 2026-04-23 18:04:15 -05:00
Author
Owner
Copy Link

@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?

<!-- gh-comment-id:3237547300 --> @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?
GiteaMirror commented 2026-04-23 18:04:15 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:3237919118 --> @Anonym001 commented on GitHub (Aug 29, 2025): i am using microg, and currently facing this exact same issue on fennec f-droid.
GiteaMirror commented 2026-04-23 18:04:15 -05:00
Author
Owner
Copy Link

@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

<!-- gh-comment-id:3239527040 --> @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)
GiteaMirror commented 2026-04-23 18:04:16 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:3251040434 --> @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.
GiteaMirror commented 2026-04-23 18:04:16 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:3339129331 --> @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).
GiteaMirror commented 2026-04-23 18:04:17 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:3555023397 --> @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.
GiteaMirror commented 2026-04-23 18:04:17 -05:00
Author
Owner
Copy Link

@Szaamaan commented on GitHub (Dec 6, 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.

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

<!-- gh-comment-id:3620472669 --> @Szaamaan commented on GitHub (Dec 6, 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). 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...
GiteaMirror commented 2026-04-23 18:04:18 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 6, 2025):

@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

<!-- gh-comment-id:3621381492 --> @pamperer562580892423 commented on GitHub (Dec 6, 2025): @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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#39299
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?