[PM-24260] Brave Android app auto fill not working in http websites #2298

Open
opened 2025-11-26 23:14:48 -06:00 by GiteaMirror · 17 comments
Owner

Originally created by @dkorecko on GitHub (Jul 29, 2025).

Steps To Reproduce

  1. Open Brave (Bitwarden installed, autofil and inline autofill enabled, Bitwarden set in Android and Brave as main auto-fill app)
  2. Navigate to any http website that you know works in Brave extension on desktop

Expected Result

Same as happens in the Brave browser with the Bitwarden browser extension, credentials should be filled in properly since it's the same website.

Actual Result

No auto-fill shows up when opening the page/clicking on any of the fields. Also, when holding down on the password field and pressing Autofill, nothing is filled in. On other sites (that have https) this does not happen on mobile. Additionally, this specific self-hosted website has no issues on Brave desktop.

Screenshots or Videos

No response

Additional Context

Same auto-fill not working happens on all my locally running services (only on Android).

Build Version

2025.6.1 20398

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Device: Samsung Galaxy S24+
  • OS Version: One UI 7
  • Keyboard: Gboard
  • Browser: Brave 1.79.126, Chromium 137.0.7151.119

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 @dkorecko on GitHub (Jul 29, 2025). ### Steps To Reproduce 1. Open Brave (Bitwarden installed, autofil and inline autofill enabled, Bitwarden set in Android and Brave as main auto-fill app) 2. Navigate to any http website that you know works in Brave extension on desktop ### Expected Result Same as happens in the Brave browser with the Bitwarden browser extension, credentials should be filled in properly since it's the same website. ### Actual Result No auto-fill shows up when opening the page/clicking on any of the fields. Also, when holding down on the password field and pressing Autofill, nothing is filled in. On other sites (that have https) this does not happen on mobile. Additionally, this specific self-hosted website has no issues on Brave desktop. ### Screenshots or Videos _No response_ ### Additional Context Same auto-fill not working happens on all my locally running services (only on Android). ### Build Version 2025.6.1 20398 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details - Device: Samsung Galaxy S24+ - OS Version: One UI 7 - Keyboard: Gboard - Browser: Brave 1.79.126, Chromium 137.0.7151.119 ### 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:14:48 -06:00
Author
Owner

@bitwarden-bot commented on GitHub (Jul 29, 2025):

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

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

@Adedamola-Aina commented on GitHub (Jul 30, 2025):

Hello @dkorecko

We use GitHub issues as a place to track bugs and other development-related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).
You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

@Adedamola-Aina commented on GitHub (Jul 30, 2025): Hello @dkorecko We use GitHub issues as a place to track bugs and other development-related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).
Author
Owner

@Turge08 commented on GitHub (Jul 30, 2025):

I can confirm I have the same issue and this was working fine about a week ago.

@Turge08 commented on GitHub (Jul 30, 2025): I can confirm I have the same issue and this was working fine about a week ago.
Author
Owner

@h44z commented on GitHub (Aug 1, 2025):

Maybe related to this? https://www.reddit.com/r/Bitwarden/comments/1mdd9b6/important_android_autofill_updates/

@h44z commented on GitHub (Aug 1, 2025): Maybe related to this? https://www.reddit.com/r/Bitwarden/comments/1mdd9b6/important_android_autofill_updates/
Author
Owner

@dkorecko commented on GitHub (Aug 2, 2025):

Maybe related to this? https://www.reddit.com/r/Bitwarden/comments/1mdd9b6/important_android_autofill_updates/

I will check when I get the 2025.7.0/1 update. However, I have Bitwarden save as service for auto-fill both in Brave and in Android settings (Samsung). No additional services allowed either.

@dkorecko commented on GitHub (Aug 2, 2025): > Maybe related to this? https://www.reddit.com/r/Bitwarden/comments/1mdd9b6/important_android_autofill_updates/ I will check when I get the 2025.7.0/1 update. However, I have Bitwarden save as service for auto-fill both in Brave and in Android settings (Samsung). No additional services allowed either.
Author
Owner

@germanikus666 commented on GitHub (Aug 3, 2025):

I have exactly the same problem that the autofill no longer works reliably on my Google Pixel 7

@germanikus666 commented on GitHub (Aug 3, 2025): I have exactly the same problem that the autofill no longer works reliably on my Google Pixel 7
Author
Owner

@Verryx-02 commented on GitHub (Aug 7, 2025):

Hi, just checking — is there already an internal fix in progress for PM-24260?
I’d be happy to investigate or even propose a PR if this hasn’t been assigned yet.
Thanks!

@Verryx-02 commented on GitHub (Aug 7, 2025): Hi, just checking — is there already an internal fix in progress for PM-24260? I’d be happy to investigate or even propose a PR if this hasn’t been assigned yet. Thanks!
Author
Owner

@dkorecko commented on GitHub (Aug 12, 2025):

Also just tested this on Vivaldi and I do not have the same issue, autofill works just fine.

@dkorecko commented on GitHub (Aug 12, 2025): Also just tested this on Vivaldi and I do not have the same issue, autofill works just fine.
Author
Owner

@Verryx-02 commented on GitHub (Aug 12, 2025):

@dkorecko Can you show me the link you used to do the tests?

@Verryx-02 commented on GitHub (Aug 12, 2025): @dkorecko Can you show me the link you used to do the tests?
Author
Owner

@dkorecko commented on GitHub (Aug 12, 2025):

@dkorecko Can you show me the link you used to do the tests?

For example:
Image

@dkorecko commented on GitHub (Aug 12, 2025): > [@dkorecko](https://github.com/dkorecko) Can you show me the link you used to do the tests? For example: <img width="379" height="485" alt="Image" src="https://github.com/user-attachments/assets/a921d921-dc7b-49eb-93da-053364cd7498" />
Author
Owner

@Verryx-02 commented on GitHub (Aug 21, 2025):

Ok, I'll take a look. It might take me a while.

@Verryx-02 commented on GitHub (Aug 21, 2025): Ok, I'll take a look. It might take me a while.
Author
Owner

@Aashishkebab commented on GitHub (Sep 2, 2025):

I reported this issue as well. It has been happening for months, every since the "redesign", and I also contacted support numerous times about it (who always eventually ghosted me and stopped responding). They also closed the issue: https://github.com/bitwarden/android/issues/5341

@Aashishkebab commented on GitHub (Sep 2, 2025): I reported this issue as well. It has been happening for months, every since the "redesign", and I also contacted support numerous times about it (who always eventually ghosted me and stopped responding). They also closed the issue: https://github.com/bitwarden/android/issues/5341
Author
Owner

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

@dkorecko We do not have any explicit restrictions on autofilling http sites. That being said, I think it would be helpful to start by confirming whether Brave and the Autofill Service are properly invoking Bitwarden. This can be done by enabling Bitwarden's Flight Recorder, navigating to the site, then focusing an input field.

Additionally, I recommend establishing a baseline by navigating to the same site on a browser that is not exhibiting the unexpected behavior.

Once captured, you have a few options:

  1. Share the logs with our support team and reference this ticket. We will review the logs and update our findings, or
  2. If you're comfortable reading logs, review them yourself and look for lines similar to the exert below. They will indicate if an Autofill request was received and if Bitwarden considered it fillable or not.
Begin processing Autofill fill request -- 1270
Parsing AssistStructure -- 1270
Autofill request isInlineEnabled=true -- 1270
Autofill request is Fillable -- 1270
Autofill request constructing FilledData
Autofill request constructing SaveInfo -- 1270
Autofill request isInCompatMode=false -- 1270
Autofill request constructing FillResponse
Autofill request isInlineCompatible=true
Autofill request success: Fillable -- 1270

One final thing; in your latest screenshot I see you have a port included in the URL. As a friendly reminder, there is a known limitation with port and path matching in Android because the Autofill Service does not provide the full URL to credential providers.

@SaintPatrck commented on GitHub (Sep 3, 2025): @dkorecko We do not have any explicit restrictions on autofilling `http` sites. That being said, I think it would be helpful to start by confirming whether Brave and the Autofill Service are properly invoking Bitwarden. This can be done by enabling Bitwarden's Flight Recorder, navigating to the site, then focusing an input field. Additionally, I recommend establishing a baseline by navigating to the same site on a browser that **is not** exhibiting the unexpected behavior. Once captured, you have a few options: 1. Share the logs with our support team and reference this ticket. We will review the logs and update our findings, or 2. If you're comfortable reading logs, review them yourself and look for lines similar to the exert below. They will indicate if an Autofill request was received and if Bitwarden considered it fillable or not. ``` Begin processing Autofill fill request -- 1270 Parsing AssistStructure -- 1270 Autofill request isInlineEnabled=true -- 1270 Autofill request is Fillable -- 1270 Autofill request constructing FilledData Autofill request constructing SaveInfo -- 1270 Autofill request isInCompatMode=false -- 1270 Autofill request constructing FillResponse Autofill request isInlineCompatible=true Autofill request success: Fillable -- 1270 ``` One final thing; in your latest screenshot I see you have a port included in the URL. As a friendly reminder, there is a known limitation with port and path matching in Android because the Autofill Service does not provide the full URL to credential providers.
Author
Owner

@mcontenti commented on GitHub (Sep 13, 2025):

I just installed Bitwarden and I'm having the same issue with Chrome on Android 15 (see exact configuration in the log below) accessing HTTP web sites (mostly devices on my local network).
I can log on all of the following devices without any problem on my PC using both Chrome and Firefox with the same synced vault.

The following log was captured trying to access a Webmin server on the local network:

Bitwarden Android
Log Start Time: 2025-09-13 11:36:14:782
Log Duration: 1h
App Version: 2025.8.1 (20670)
Build: release/standard
Operating System: 15 (35)
Device: motorola motorola edge 50 neo
Fingerprint: motorola/vienna_g_syses/vienna:15/V1UIS35H.11-39-28-1/c7a74f-0be2bf:user/release-keys
2025-09-13 11:36:14:786 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2025-09-13 11:36:14:787 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2025-09-13 11:36:14:831 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2025-09-13 11:36:18:883 – DEBUG – b – Network status change: Wifi(strength=EXCELLENT)
2025-09-13 11:36:18:930 – DEBUG – c – App is backgrounded
2025-09-13 11:36:21:945 – DEBUG – b – Network status change: Wifi(strength=GOOD)
2025-09-13 11:36:24:958 – DEBUG – b – Network status change: None
2025-09-13 11:36:49:327 – DEBUG – c – App is foregrounded

Basically it's like nothing happened, though I have a valid login saved for the URL. I didn't get any prompt on the keyboard.

The following are two attempts to log into a FritzBox router - both unsuccessful. The login page shows a list of user names. At first I switched to a different user and got to the password box: I was prompted with saved logins on the keyboard, but the password wasn't filled as I tapped one of them:

2025-09-13 11:18:45:852 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 1388
2025-09-13 11:18:45:852 – DEBUG – a – Parsing AssistStructure -- 1388
2025-09-13 11:18:45:869 – DEBUG – a – Autofill request isInlineEnabled=true -- 1388
2025-09-13 11:18:45:870 – DEBUG – c – Autofill request constructing FilledData
2025-09-13 11:18:45:870 – DEBUG – c – Autofill request is Fillable -- 1388
2025-09-13 11:18:45:972 – DEBUG – c – Autofill request constructing SaveInfo -- 1388
2025-09-13 11:18:45:972 – DEBUG – c – Autofill request isInCompatMode=false -- 1388
2025-09-13 11:18:45:973 – DEBUG – c – Autofill request constructing FillResponse
2025-09-13 11:18:45:978 – DEBUG – b – Autofill request isInlineCompatible=true
2025-09-13 11:18:45:980 – DEBUG – b – Autofill request isInlineCompatible=true
2025-09-13 11:18:45:982 – DEBUG – b – Autofill request isInlineCompatible=true
2025-09-13 11:18:45:984 – DEBUG – b – Autofill request isInlineCompatible=true
2025-09-13 11:18:45:984 – DEBUG – c – Autofill request success: Fillable -- 1388

Next, I didn't switch user name and reloaded the page. Getting to the password box I didn't get any login prompt on the keyboard:

2025-09-13 11:19:03:587 – DEBUG – a – Parsing AssistStructure -- null
2025-09-13 11:19:03:587 – DEBUG – a – Autofill request isInlineEnabled=true -- null
2025-09-13 11:19:03:590 – DEBUG – e – Autofill -- Cipher found
2025-09-13 11:19:03:602 – DEBUG – c – Autofill request constructing FilledData
2025-09-13 11:19:03:603 – DEBUG – T – Autofill success

This behavior is consistent: no user switch, no login prompt.

@mcontenti commented on GitHub (Sep 13, 2025): I just installed Bitwarden and I'm having the same issue with Chrome on Android 15 (see exact configuration in the log below) accessing HTTP web sites (mostly devices on my local network). I can log on all of the following devices without any problem on my PC using both Chrome and Firefox with the same synced vault. The following log was captured trying to access a Webmin server on the local network: ``` Bitwarden Android Log Start Time: 2025-09-13 11:36:14:782 Log Duration: 1h App Version: 2025.8.1 (20670) Build: release/standard Operating System: 15 (35) Device: motorola motorola edge 50 neo Fingerprint: motorola/vienna_g_syses/vienna:15/V1UIS35H.11-39-28-1/c7a74f-0be2bf:user/release-keys 2025-09-13 11:36:14:786 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-09-13 11:36:14:787 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-09-13 11:36:14:831 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-09-13 11:36:18:883 – DEBUG – b – Network status change: Wifi(strength=EXCELLENT) 2025-09-13 11:36:18:930 – DEBUG – c – App is backgrounded 2025-09-13 11:36:21:945 – DEBUG – b – Network status change: Wifi(strength=GOOD) 2025-09-13 11:36:24:958 – DEBUG – b – Network status change: None 2025-09-13 11:36:49:327 – DEBUG – c – App is foregrounded ``` Basically it's like nothing happened, though I have a valid login saved for the URL. I didn't get any prompt on the keyboard. The following are two attempts to log into a FritzBox router - both unsuccessful. The login page shows a list of user names. At first I switched to a different user and got to the password box: I was prompted with saved logins on the keyboard, but the password wasn't filled as I tapped one of them: ``` 2025-09-13 11:18:45:852 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 1388 2025-09-13 11:18:45:852 – DEBUG – a – Parsing AssistStructure -- 1388 2025-09-13 11:18:45:869 – DEBUG – a – Autofill request isInlineEnabled=true -- 1388 2025-09-13 11:18:45:870 – DEBUG – c – Autofill request constructing FilledData 2025-09-13 11:18:45:870 – DEBUG – c – Autofill request is Fillable -- 1388 2025-09-13 11:18:45:972 – DEBUG – c – Autofill request constructing SaveInfo -- 1388 2025-09-13 11:18:45:972 – DEBUG – c – Autofill request isInCompatMode=false -- 1388 2025-09-13 11:18:45:973 – DEBUG – c – Autofill request constructing FillResponse 2025-09-13 11:18:45:978 – DEBUG – b – Autofill request isInlineCompatible=true 2025-09-13 11:18:45:980 – DEBUG – b – Autofill request isInlineCompatible=true 2025-09-13 11:18:45:982 – DEBUG – b – Autofill request isInlineCompatible=true 2025-09-13 11:18:45:984 – DEBUG – b – Autofill request isInlineCompatible=true 2025-09-13 11:18:45:984 – DEBUG – c – Autofill request success: Fillable -- 1388 ``` Next, I didn't switch user name and reloaded the page. Getting to the password box I didn't get any login prompt on the keyboard: ``` 2025-09-13 11:19:03:587 – DEBUG – a – Parsing AssistStructure -- null 2025-09-13 11:19:03:587 – DEBUG – a – Autofill request isInlineEnabled=true -- null 2025-09-13 11:19:03:590 – DEBUG – e – Autofill -- Cipher found 2025-09-13 11:19:03:602 – DEBUG – c – Autofill request constructing FilledData 2025-09-13 11:19:03:603 – DEBUG – T – Autofill success ``` This behavior is consistent: no user switch, no login prompt.
Author
Owner

@kevsei commented on GitHub (Sep 18, 2025):

Hey, i have the same issues with http Sites (internal Services). Pls fix this. Its only in Android. At PC all Works perfect.

@kevsei commented on GitHub (Sep 18, 2025): Hey, i have the same issues with http Sites (internal Services). Pls fix this. Its only in Android. At PC all Works perfect.
Author
Owner

@ssunny1081 commented on GitHub (Nov 1, 2025):

Samsung TAB S11, Chrome 141 on Android 16, same issue, http sites are not recognized at all. Sames sites work fine on Windows. Other https sites are working fine on Android as well.

@ssunny1081 commented on GitHub (Nov 1, 2025): Samsung TAB S11, Chrome 141 on Android 16, same issue, http sites are not recognized at all. Sames sites work fine on Windows. Other https sites are working fine on Android as well.
Author
Owner

@fichte-112 commented on GitHub (Nov 22, 2025):

I have the same problem. Http sites do not work on Android.

@fichte-112 commented on GitHub (Nov 22, 2025): I have the same problem. Http sites do not work on Android.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2298