github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-16 19:04:56 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #5609] [PM-24260] Brave Android app auto fill not working in http websites #28185

New Issue
Open
opened 2026-04-18 12:06:30 -05:00 by GiteaMirror · 39 comments
GiteaMirror commented 2026-04-18 12:06:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @dkorecko on GitHub (Jul 29, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5609

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

@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

<!-- gh-comment-id:3132102194 --> @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
GiteaMirror commented 2026-04-18 12:06:33 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3136002764 --> @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/).
GiteaMirror commented 2026-04-18 12:06:33 -05:00
Author
Owner
Copy Link
Copy Source

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

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

<!-- gh-comment-id:3136236355 --> @Turge08 commented on GitHub (Jul 30, 2025): I can confirm I have the same issue and this was working fine about a week ago.
GiteaMirror commented 2026-04-18 12:06:34 -05:00
Author
Owner
Copy Link
Copy Source

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

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

<!-- gh-comment-id:3145821151 --> @h44z commented on GitHub (Aug 1, 2025): Maybe related to this? https://www.reddit.com/r/Bitwarden/comments/1mdd9b6/important_android_autofill_updates/
GiteaMirror commented 2026-04-18 12:06:35 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3146394068 --> @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.
GiteaMirror commented 2026-04-18 12:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@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

<!-- gh-comment-id:3146993214 --> @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
GiteaMirror commented 2026-04-18 12:06:35 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3162495823 --> @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!
GiteaMirror commented 2026-04-18 12:06:36 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3178837324 --> @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.
GiteaMirror commented 2026-04-18 12:06:36 -05:00
Author
Owner
Copy Link
Copy Source

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

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

<!-- gh-comment-id:3178920858 --> @Verryx-02 commented on GitHub (Aug 12, 2025): @dkorecko Can you show me the link you used to do the tests?
GiteaMirror commented 2026-04-18 12:06:37 -05:00
Author
Owner
Copy Link
Copy Source

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

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

For example:
Image

<!-- gh-comment-id:3179191559 --> @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" />
GiteaMirror commented 2026-04-18 12:06:37 -05:00
Author
Owner
Copy Link
Copy Source

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

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

<!-- gh-comment-id:3209666279 --> @Verryx-02 commented on GitHub (Aug 21, 2025): Ok, I'll take a look. It might take me a while.
GiteaMirror commented 2026-04-18 12:06:39 -05:00
Author
Owner
Copy Link
Copy Source

@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

<!-- gh-comment-id:3246306245 --> @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
GiteaMirror commented 2026-04-18 12:06:39 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3251017010 --> @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.
GiteaMirror commented 2026-04-18 12:06:40 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3288011158 --> @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.
GiteaMirror commented 2026-04-18 12:06:41 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3307476853 --> @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.
GiteaMirror commented 2026-04-18 12:06:43 -05:00
Author
Owner
Copy Link
Copy Source

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

<!-- gh-comment-id:3476065463 --> @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.
GiteaMirror commented 2026-04-18 12:06:46 -05:00
Author
Owner
Copy Link
Copy Source

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

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

<!-- gh-comment-id:3566424551 --> @fichte-112 commented on GitHub (Nov 22, 2025): I have the same problem. Http sites do not work on Android.
GiteaMirror commented 2026-04-18 12:06:47 -05:00
Author
Owner
Copy Link
Copy Source

@Kazenn commented on GitHub (Nov 28, 2025):

Same here...

<!-- gh-comment-id:3590629790 --> @Kazenn commented on GitHub (Nov 28, 2025): Same here...
GiteaMirror commented 2026-04-18 12:06:47 -05:00
Author
Owner
Copy Link
Copy Source

@nick-77 commented on GitHub (Dec 12, 2025):

Is there an update on this? Facing the same issue since months

<!-- gh-comment-id:3648318462 --> @nick-77 commented on GitHub (Dec 12, 2025): Is there an update on this? Facing the same issue since months
GiteaMirror commented 2026-04-18 12:06:48 -05:00
Author
Owner
Copy Link
Copy Source

@mprenditore commented on GitHub (Dec 12, 2025):

Same here, hope it gets solved soon!

<!-- gh-comment-id:3648327479 --> @mprenditore commented on GitHub (Dec 12, 2025): Same here, hope it gets solved soon!
GiteaMirror commented 2026-04-18 12:06:48 -05:00
Author
Owner
Copy Link
Copy Source

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

@SaintPatrck I now also tried to autofill on a http site. It was a FRITZ!Box site, which is only available on http. - On desktop, the browser extension can autofill.

I activated the flight recorder and tried to autofill. I changed browsers in between, so I don't know how helpful this log is now. I could try to do it again, if you need it more specific.

I think I started with Brave, which didn't work. Then I also changed to Firefox, Vivaldi and Chrome (that might not be the order in the log!). Interestingly, autofill on Firefox and Vivaldi worked, but not on Brave and Chrome (despite the autofill integration for Chrome and Brave is enabled).

Bitwarden Android
Log Start Time: 2025-12-13 00:16:07:399
Log Duration: 1d
App Version: 2025.12.0 (21003)
Build: release/standard
Operating System: 15 (35)
Device: Fairphone FP5
Fingerprint: Fairphone/FP5/FP5:15/AQ3A.240912.001/VT2F:user/release-keys
2025-12-13 00:16:07:409 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2025-12-13 00:16:07:469 – 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-12-13 00:16:09:297 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2025-12-13 00:16:10:446 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.vault.feature.vault.VaultRoute in com.x8bit.bitwarden.ui.vault.feature.vault.VaultGraphRoute
2025-12-13 00:16:11:996 – DEBUG – b – App is backgrounded
2025-12-13 00:16:40:058 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 402
2025-12-13 00:16:40:059 – DEBUG – a – Parsing AssistStructure -- 402
2025-12-13 00:16:40:080 – DEBUG – a – Autofill request isInlineEnabled=true -- 402
2025-12-13 00:16:40:080 – DEBUG – c – Autofill request is Fillable -- 402
2025-12-13 00:16:40:080 – DEBUG – c – Autofill request constructing FilledData
2025-12-13 00:16:40:147 – DEBUG – c – Autofill request constructing SaveInfo -- 402
2025-12-13 00:16:40:147 – DEBUG – c – Autofill request isInCompatMode=false -- 402
2025-12-13 00:16:40:148 – DEBUG – c – Autofill request constructing FillResponse
2025-12-13 00:16:40:150 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-13 00:16:40:152 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-13 00:16:40:155 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-13 00:16:40:156 – DEBUG – c – Autofill request success: Fillable -- 402
2025-12-13 00:16:43:990 – DEBUG – b – App is foregrounded
2025-12-13 00:16:44:030 – DEBUG – r – Autofill -- Cipher found
2025-12-13 00:16:44:030 – DEBUG – a – Parsing AssistStructure -- null
2025-12-13 00:16:44:038 – DEBUG – a – Autofill request isInlineEnabled=true -- null
2025-12-13 00:16:44:039 – DEBUG – c – Autofill request constructing FilledData
2025-12-13 00:16:44:044 – DEBUG – c0 – Autofill success
2025-12-13 00:16:44:783 – DEBUG – b – App is backgrounded
2025-12-13 00:17:04:789 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 404
2025-12-13 00:17:04:792 – DEBUG – a – Parsing AssistStructure -- 404
2025-12-13 00:17:04:802 – DEBUG – a – Autofill request isInlineEnabled=true -- 404
2025-12-13 00:17:04:802 – DEBUG – c – Autofill request constructing FilledData
2025-12-13 00:17:04:802 – DEBUG – c – Autofill request is Fillable -- 404
2025-12-13 00:17:04:831 – DEBUG – c – Autofill request constructing FillResponse
2025-12-13 00:17:04:831 – DEBUG – c – Autofill request constructing SaveInfo -- 404
2025-12-13 00:17:04:831 – DEBUG – c – Autofill request isInCompatMode=false -- 404
2025-12-13 00:17:04:832 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-13 00:17:04:834 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-13 00:17:04:834 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-13 00:17:04:834 – DEBUG – c – Autofill request success: Fillable -- 404
2025-12-13 00:17:06:605 – DEBUG – r – Autofill -- Cipher found
2025-12-13 00:17:06:606 – DEBUG – a – Parsing AssistStructure -- null
2025-12-13 00:17:06:614 – DEBUG – a – Autofill request isInlineEnabled=true -- null
2025-12-13 00:17:06:637 – DEBUG – b – App is foregrounded
2025-12-13 00:17:06:646 – DEBUG – c – Autofill request constructing FilledData
2025-12-13 00:17:06:647 – DEBUG – c0 – Autofill success
2025-12-13 00:17:07:407 – DEBUG – b – App is backgrounded
2025-12-13 00:17:17:756 – DEBUG – k1 – Network status change: None
2025-12-13 00:17:53:805 – DEBUG – b – App is foregrounded
2025-12-13 00:17:53:807 – DEBUG – k1 – Network status change: Wifi(strength=EXCELLENT)
2025-12-13 00:17:55:821 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2025-12-13 00:17:55:827 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute

<!-- gh-comment-id:3648575269 --> @pamperer562580892423 commented on GitHub (Dec 13, 2025): @SaintPatrck I now also tried to autofill on a http site. It was a FRITZ!Box site, which is only available on http. - On desktop, the browser extension can autofill. I activated the flight recorder and tried to autofill. I changed browsers in between, so I don't know how helpful this log is now. I could try to do it again, if you need it more specific. I think I started with Brave, which didn't work. Then I also changed to Firefox, Vivaldi and Chrome (that might not be the order in the log!). Interestingly, autofill on Firefox and Vivaldi worked, but not on Brave and Chrome (despite the autofill integration for Chrome and Brave is enabled). Bitwarden Android Log Start Time: 2025-12-13 00:16:07:399 Log Duration: 1d App Version: 2025.12.0 (21003) Build: release/standard Operating System: 15 (35) Device: Fairphone FP5 Fingerprint: Fairphone/FP5/FP5:15/AQ3A.240912.001/VT2F:user/release-keys 2025-12-13 00:16:07:409 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-12-13 00:16:07:469 – 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-12-13 00:16:09:297 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-12-13 00:16:10:446 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.vault.feature.vault.VaultRoute in com.x8bit.bitwarden.ui.vault.feature.vault.VaultGraphRoute 2025-12-13 00:16:11:996 – DEBUG – b – App is backgrounded 2025-12-13 00:16:40:058 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 402 2025-12-13 00:16:40:059 – DEBUG – a – Parsing AssistStructure -- 402 2025-12-13 00:16:40:080 – DEBUG – a – Autofill request isInlineEnabled=true -- 402 2025-12-13 00:16:40:080 – DEBUG – c – Autofill request is Fillable -- 402 2025-12-13 00:16:40:080 – DEBUG – c – Autofill request constructing FilledData 2025-12-13 00:16:40:147 – DEBUG – c – Autofill request constructing SaveInfo -- 402 2025-12-13 00:16:40:147 – DEBUG – c – Autofill request isInCompatMode=false -- 402 2025-12-13 00:16:40:148 – DEBUG – c – Autofill request constructing FillResponse 2025-12-13 00:16:40:150 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-13 00:16:40:152 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-13 00:16:40:155 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-13 00:16:40:156 – DEBUG – c – Autofill request success: Fillable -- 402 2025-12-13 00:16:43:990 – DEBUG – b – App is foregrounded 2025-12-13 00:16:44:030 – DEBUG – r – Autofill -- Cipher found 2025-12-13 00:16:44:030 – DEBUG – a – Parsing AssistStructure -- null 2025-12-13 00:16:44:038 – DEBUG – a – Autofill request isInlineEnabled=true -- null 2025-12-13 00:16:44:039 – DEBUG – c – Autofill request constructing FilledData 2025-12-13 00:16:44:044 – DEBUG – c0 – Autofill success 2025-12-13 00:16:44:783 – DEBUG – b – App is backgrounded 2025-12-13 00:17:04:789 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 404 2025-12-13 00:17:04:792 – DEBUG – a – Parsing AssistStructure -- 404 2025-12-13 00:17:04:802 – DEBUG – a – Autofill request isInlineEnabled=true -- 404 2025-12-13 00:17:04:802 – DEBUG – c – Autofill request constructing FilledData 2025-12-13 00:17:04:802 – DEBUG – c – Autofill request is Fillable -- 404 2025-12-13 00:17:04:831 – DEBUG – c – Autofill request constructing FillResponse 2025-12-13 00:17:04:831 – DEBUG – c – Autofill request constructing SaveInfo -- 404 2025-12-13 00:17:04:831 – DEBUG – c – Autofill request isInCompatMode=false -- 404 2025-12-13 00:17:04:832 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-13 00:17:04:834 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-13 00:17:04:834 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-13 00:17:04:834 – DEBUG – c – Autofill request success: Fillable -- 404 2025-12-13 00:17:06:605 – DEBUG – r – Autofill -- Cipher found 2025-12-13 00:17:06:606 – DEBUG – a – Parsing AssistStructure -- null 2025-12-13 00:17:06:614 – DEBUG – a – Autofill request isInlineEnabled=true -- null 2025-12-13 00:17:06:637 – DEBUG – b – App is foregrounded 2025-12-13 00:17:06:646 – DEBUG – c – Autofill request constructing FilledData 2025-12-13 00:17:06:647 – DEBUG – c0 – Autofill success 2025-12-13 00:17:07:407 – DEBUG – b – App is backgrounded 2025-12-13 00:17:17:756 – DEBUG – k1 – Network status change: None 2025-12-13 00:17:53:805 – DEBUG – b – App is foregrounded 2025-12-13 00:17:53:807 – DEBUG – k1 – Network status change: Wifi(strength=EXCELLENT) 2025-12-13 00:17:55:821 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2025-12-13 00:17:55:827 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
GiteaMirror commented 2026-04-18 12:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@Daniel-PT commented on GitHub (Dec 20, 2025):

I also have this problem in Chrome and Brave.

<!-- gh-comment-id:3677406226 --> @Daniel-PT commented on GitHub (Dec 20, 2025): I also have this problem in Chrome and Brave.
GiteaMirror commented 2026-04-18 12:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@mprenditore commented on GitHub (Dec 20, 2025):

Here my logs when trying to access the same url with HTTP and with HTTPS (my technetium server that supports both), on Brave (tried Chrome as well and it's the same result).
Steps followed:

  1. Open the browser on the page with login
  2. Switch to bit warden options to enable flight recording and enable it
  3. Switch back to the browser and refresh the page (just in case, not really do anything)
  4. Switch back to bitwarden to disable logging and save the file

As you can see, it looks like with http website it doesn't get anything, it's not very verbose the log.

HTTP

Bitwarden Android
Log Start Time: 2025-12-20 10:38:59:773
Log Duration: 1h
App Version: 2025.12.0 (21003)
Build: release/standard
Operating System: 16 (36)
Device: google Pixel 10 Pro XL
Fingerprint: google/mustang/mustang:16/BD3A.251105.010.E1/14337626:user/release-keys
2025-12-20 10:38:59:779 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2025-12-20 10:38:59:809 – 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-12-20 10:39:05:089 – DEBUG – b – App is backgrounded
2025-12-20 10:39:14:101 – DEBUG – b – App is foregrounded

HTTPS

Bitwarden Android
Log Start Time: 2025-12-20 10:39:18:126
Log Duration: 1d
App Version: 2025.12.0 (21003)
Build: release/standard
Operating System: 16 (36)
Device: google Pixel 10 Pro XL
Fingerprint: google/mustang/mustang:16/BD3A.251105.010.E1/14337626:user/release-keys
2025-12-20 10:39:18:131 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2025-12-20 10:39:18:156 – 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-12-20 10:39:20:339 – DEBUG – b – App is backgrounded
2025-12-20 10:39:23:645 – DEBUG – k1 – Network status change: Wifi(strength=FAIR)
2025-12-20 10:39:24:613 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 2068
2025-12-20 10:39:24:613 – DEBUG – a – Parsing AssistStructure -- 2068
2025-12-20 10:39:24:620 – DEBUG – c – Autofill request is Fillable -- 2068
2025-12-20 10:39:24:620 – DEBUG – c – Autofill request constructing FilledData
2025-12-20 10:39:24:620 – DEBUG – a – Autofill request isInlineEnabled=true -- 2068
2025-12-20 10:39:24:642 – DEBUG – c – Autofill request constructing SaveInfo -- 2068
2025-12-20 10:39:24:642 – DEBUG – c – Autofill request isInCompatMode=false -- 2068
2025-12-20 10:39:24:643 – DEBUG – c – Autofill request constructing FillResponse
2025-12-20 10:39:24:646 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-20 10:39:24:646 – DEBUG – c – Autofill request success: Fillable -- 2068
2025-12-20 10:39:24:646 – DEBUG – c – Autofill request isInlineCompatible=true
2025-12-20 10:39:26:765 – DEBUG – k1 – Network status change: Wifi(strength=GOOD)
2025-12-20 10:39:27:546 – DEBUG – b – App is foregrounded
<!-- gh-comment-id:3677659630 --> @mprenditore commented on GitHub (Dec 20, 2025): Here my logs when trying to access the same url with HTTP and with HTTPS (my technetium server that supports both), on Brave (tried Chrome as well and it's the same result). Steps followed: 1. Open the browser on the page with login 2. Switch to bit warden options to enable flight recording and enable it 3. Switch back to the browser and refresh the page (just in case, not really do anything) 4. Switch back to bitwarden to disable logging and save the file As you can see, it looks like with http website it doesn't get anything, it's not very verbose the log. ## HTTP ``` Bitwarden Android Log Start Time: 2025-12-20 10:38:59:773 Log Duration: 1h App Version: 2025.12.0 (21003) Build: release/standard Operating System: 16 (36) Device: google Pixel 10 Pro XL Fingerprint: google/mustang/mustang:16/BD3A.251105.010.E1/14337626:user/release-keys 2025-12-20 10:38:59:779 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-12-20 10:38:59:809 – 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-12-20 10:39:05:089 – DEBUG – b – App is backgrounded 2025-12-20 10:39:14:101 – DEBUG – b – App is foregrounded ``` ## HTTPS ``` Bitwarden Android Log Start Time: 2025-12-20 10:39:18:126 Log Duration: 1d App Version: 2025.12.0 (21003) Build: release/standard Operating System: 16 (36) Device: google Pixel 10 Pro XL Fingerprint: google/mustang/mustang:16/BD3A.251105.010.E1/14337626:user/release-keys 2025-12-20 10:39:18:131 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-12-20 10:39:18:156 – 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-12-20 10:39:20:339 – DEBUG – b – App is backgrounded 2025-12-20 10:39:23:645 – DEBUG – k1 – Network status change: Wifi(strength=FAIR) 2025-12-20 10:39:24:613 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 2068 2025-12-20 10:39:24:613 – DEBUG – a – Parsing AssistStructure -- 2068 2025-12-20 10:39:24:620 – DEBUG – c – Autofill request is Fillable -- 2068 2025-12-20 10:39:24:620 – DEBUG – c – Autofill request constructing FilledData 2025-12-20 10:39:24:620 – DEBUG – a – Autofill request isInlineEnabled=true -- 2068 2025-12-20 10:39:24:642 – DEBUG – c – Autofill request constructing SaveInfo -- 2068 2025-12-20 10:39:24:642 – DEBUG – c – Autofill request isInCompatMode=false -- 2068 2025-12-20 10:39:24:643 – DEBUG – c – Autofill request constructing FillResponse 2025-12-20 10:39:24:646 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-20 10:39:24:646 – DEBUG – c – Autofill request success: Fillable -- 2068 2025-12-20 10:39:24:646 – DEBUG – c – Autofill request isInlineCompatible=true 2025-12-20 10:39:26:765 – DEBUG – k1 – Network status change: Wifi(strength=GOOD) 2025-12-20 10:39:27:546 – DEBUG – b – App is foregrounded ```
GiteaMirror commented 2026-04-18 12:06:50 -05:00
Author
Owner
Copy Link
Copy Source

@kkplein commented on GitHub (Dec 21, 2025):

It is remarkable (for a commercial piece of software) how long this quite significant bug has existed, and how little activity (in getting it solved) seems to be taking place.

<!-- gh-comment-id:3679082650 --> @kkplein commented on GitHub (Dec 21, 2025): It is remarkable (for a commercial piece of software) how long this quite significant bug has existed, and how little activity (in getting it solved) seems to be taking place.
GiteaMirror commented 2026-04-18 12:06:50 -05:00
Author
Owner
Copy Link
Copy Source

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

It is remarkable (for a commercial piece of software) how long this quite significant bug has existed, and how little activity (in getting it solved) seems to be taking place.

I agree with you. I've been trying to figure out the cause of the problem for a while, but I still don't understand the code well enough to fix it.
I hope the maintainers fix this asap

<!-- gh-comment-id:3679085935 --> @Verryx-02 commented on GitHub (Dec 21, 2025): > It is remarkable (for a commercial piece of software) how long this quite significant bug has existed, and how little activity (in getting it solved) seems to be taking place. I agree with you. I've been trying to figure out the cause of the problem for a while, but I still don't understand the code well enough to fix it. I hope the maintainers fix this asap
GiteaMirror commented 2026-04-18 12:06:51 -05:00
Author
Owner
Copy Link
Copy Source

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

@kkplein and @Verryx-02 One of the BW developers asked on September 4 for some Flight Recorder logs and got only one response to that. So, if you can, provide some further logs.

<!-- gh-comment-id:3679088980 --> @pamperer562580892423 commented on GitHub (Dec 21, 2025): @kkplein and @Verryx-02 One of the BW developers [asked on September 4](https://github.com/bitwarden/android/issues/5609#issuecomment-3251017010) for some Flight Recorder logs and got only one response to that. So, if you can, provide some further logs.
GiteaMirror commented 2026-04-18 12:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@mprenditore commented on GitHub (Dec 21, 2025):

@kkplein and @Verryx-02 One of the BW developers asked on September 4 for some Flight Recorder logs and got only one response to that. So, if you can, provide some further logs.

I've replied and shared the flight record logs as well, they should all be the same across devices. They don't have lot of info. We need a deeper debug log IMHO.

Anyway since it happens on every Android device with specific browser, is something easy for them to replicate and debug deeper.

<!-- gh-comment-id:3679111267 --> @mprenditore commented on GitHub (Dec 21, 2025): > @kkplein and @Verryx-02 One of the BW developers [asked on September 4](https://github.com/bitwarden/android/issues/5609#issuecomment-3251017010) for some Flight Recorder logs and got only one response to that. So, if you can, provide some further logs. I've replied and shared the flight record logs as well, they should all be the same across devices. They don't have lot of info. We need a deeper debug log IMHO. Anyway since it happens on every Android device with specific browser, is something easy for them to replicate and debug deeper.
GiteaMirror commented 2026-04-18 12:06:52 -05:00
Author
Owner
Copy Link
Copy Source

@stevenwashere commented on GitHub (Dec 23, 2025):

Have had this problem for a long time and just blamed brave but it turns out I am experiencing the same issue. It's specifically on http sites which is why it felt inconsistent. Notably if I use the auto fill option from my quick settings it does fill correctly.

Http site - Firefox (this is functional)

Bitwarden Android
Log Start Time: 2025-12-23 08:02:06:682
Log Duration: 1h
App Version: 2025.12.0 (21003)
Build: release/standard
Operating System: 16 (36)
Device: OnePlus CPH2551
Fingerprint: OnePlus/CPH2551/OP5973L1:16/BP2A.250605.015/T.R4T3.1618e49_af6e56_af6e54:user/release-keys
2025-12-23 08:02:06:687 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
Bitwarden Android
Log Start Time: 2025-12-23 08:02:06:682
Log Duration: 1h
App Version: 2025.12.0 (21003)
Build: release/standard
Operating System: 16 (36)
Device: OnePlus CPH2551
Fingerprint: OnePlus/CPH2551/OP5973L1:16/BP2A.250605.015/T.R4T3.1618e49_af6e56_af6e54:user/release-keys
2025-12-23 08:02:06:731 – 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-12-23 08:02:09:861 – DEBUG – b – App is backgrounded
2025-12-23 08:02:19:340 – DEBUG – a – Parsing AssistStructure -- 1440
2025-12-23 08:02:19:340 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 1440
2025-12-23 08:02:19:352 – DEBUG – c – Autofill request is Fillable -- 1440
2025-12-23 08:02:19:352 – DEBUG – a – Autofill request isInlineEnabled=false -- 1440
2025-12-23 08:02:19:352 – DEBUG – c – Autofill request constructing FilledData
2025-12-23 08:02:19:427 – DEBUG – c – Autofill request constructing SaveInfo -- 1440
2025-12-23 08:02:19:428 – DEBUG – c – Autofill request isInCompatMode=false -- 1440
2025-12-23 08:02:19:428 – DEBUG – c – Autofill request constructing FillResponse
2025-12-23 08:02:19:443 – DEBUG – c – Autofill request success: Fillable -- 1440
2025-12-23 08:02:25:938 – DEBUG – b – App is foregrounded
2025-12-23 08:02:25:964 – DEBUG – r – Autofill -- Cipher found
2025-12-23 08:02:25:964 – DEBUG – a – Parsing AssistStructure -- null
2025-12-23 08:02:25:969 – DEBUG – c – Autofill request constructing FilledData
2025-12-23 08:02:25:969 – DEBUG – c0 – Autofill success
2025-12-23 08:02:25:969 – DEBUG – a – Autofill request isInlineEnabled=false -- null
2025-12-23 08:02:26:715 – DEBUG – b – App is backgrounded
2025-12-23 08:02:29:610 – DEBUG – b – App is foregrounded

Http site brave ( not working also chrome doesn't work but I didn't record logs from there. Both bw settings to work with these browsers are enabled)

Bitwarden Android
Log Start Time: 2025-12-23 08:00:27:724
Log Duration: 1h
App Version: 2025.12.0 (21003)
Build: release/standard
Operating System: 16 (36)
Device: OnePlus CPH2551
Fingerprint: OnePlus/CPH2551/OP5973L1:16/BP2A.250605.015/T.R4T3.1618e49_af6e56_af6e54:user/release-keys
2025-12-23 08:00:27:728 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2025-12-23 08:00:27:767 – 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-12-23 08:00:31:212 – DEBUG – b – App is backgrounded
2025-12-23 08:00:43:175 – DEBUG – b – App is foregrounded

I also do still get that bug where sometimes when prompted to auto fill on a working https site it won't auto fill and it'll still prompt as is the vault is locked despite me unlocking it. But that doesn't belong here I guess. Oh well.

<!-- gh-comment-id:3687175964 --> @stevenwashere commented on GitHub (Dec 23, 2025): Have had this problem for a long time and just blamed brave but it turns out I am experiencing the same issue. It's specifically on http sites which is why it felt inconsistent. Notably if I use the auto fill option from my quick settings it does fill correctly. Http site - Firefox (this is functional) ``` Bitwarden Android Log Start Time: 2025-12-23 08:02:06:682 Log Duration: 1h App Version: 2025.12.0 (21003) Build: release/standard Operating System: 16 (36) Device: OnePlus CPH2551 Fingerprint: OnePlus/CPH2551/OP5973L1:16/BP2A.250605.015/T.R4T3.1618e49_af6e56_af6e54:user/release-keys 2025-12-23 08:02:06:687 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute Bitwarden Android Log Start Time: 2025-12-23 08:02:06:682 Log Duration: 1h App Version: 2025.12.0 (21003) Build: release/standard Operating System: 16 (36) Device: OnePlus CPH2551 Fingerprint: OnePlus/CPH2551/OP5973L1:16/BP2A.250605.015/T.R4T3.1618e49_af6e56_af6e54:user/release-keys 2025-12-23 08:02:06:731 – 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-12-23 08:02:09:861 – DEBUG – b – App is backgrounded 2025-12-23 08:02:19:340 – DEBUG – a – Parsing AssistStructure -- 1440 2025-12-23 08:02:19:340 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 1440 2025-12-23 08:02:19:352 – DEBUG – c – Autofill request is Fillable -- 1440 2025-12-23 08:02:19:352 – DEBUG – a – Autofill request isInlineEnabled=false -- 1440 2025-12-23 08:02:19:352 – DEBUG – c – Autofill request constructing FilledData 2025-12-23 08:02:19:427 – DEBUG – c – Autofill request constructing SaveInfo -- 1440 2025-12-23 08:02:19:428 – DEBUG – c – Autofill request isInCompatMode=false -- 1440 2025-12-23 08:02:19:428 – DEBUG – c – Autofill request constructing FillResponse 2025-12-23 08:02:19:443 – DEBUG – c – Autofill request success: Fillable -- 1440 2025-12-23 08:02:25:938 – DEBUG – b – App is foregrounded 2025-12-23 08:02:25:964 – DEBUG – r – Autofill -- Cipher found 2025-12-23 08:02:25:964 – DEBUG – a – Parsing AssistStructure -- null 2025-12-23 08:02:25:969 – DEBUG – c – Autofill request constructing FilledData 2025-12-23 08:02:25:969 – DEBUG – c0 – Autofill success 2025-12-23 08:02:25:969 – DEBUG – a – Autofill request isInlineEnabled=false -- null 2025-12-23 08:02:26:715 – DEBUG – b – App is backgrounded 2025-12-23 08:02:29:610 – DEBUG – b – App is foregrounded ``` Http site brave ( not working also chrome doesn't work but I didn't record logs from there. Both bw settings to work with these browsers are enabled) ``` Bitwarden Android Log Start Time: 2025-12-23 08:00:27:724 Log Duration: 1h App Version: 2025.12.0 (21003) Build: release/standard Operating System: 16 (36) Device: OnePlus CPH2551 Fingerprint: OnePlus/CPH2551/OP5973L1:16/BP2A.250605.015/T.R4T3.1618e49_af6e56_af6e54:user/release-keys 2025-12-23 08:00:27:728 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2025-12-23 08:00:27:767 – 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-12-23 08:00:31:212 – DEBUG – b – App is backgrounded 2025-12-23 08:00:43:175 – DEBUG – b – App is foregrounded ``` I also do still get that bug where sometimes when prompted to auto fill on a working https site it won't auto fill and it'll still prompt as is the vault is locked despite me unlocking it. But that doesn't belong here I guess. Oh well.
GiteaMirror commented 2026-04-18 12:06:52 -05:00
Author
Owner
Copy Link
Copy Source

@SaintPatrck commented on GitHub (Dec 29, 2025):

Hi all,

Thank you for providing logs. Unfortunately the logs indicate Bitwarden did not receive an autofill request in the described failure scenarios. That means Bitwarden has nothing it can evaluate to determine if the request is from an HTTP or HTTPS site to accept or reject it. What's being described, and backed up by the logs, indicates an issue between the website, browser, and/or Android's Autofill service resulting in the autofill request, whether triggered by the site or not, never making it to Bitwarden.

For more context; if we wanted to prevent autofilling HTTP sites we would have to evaluate the autofill request metadata, then explicitly reject it. Even if we did perform HTTP filtering (which we DO NOT), we would not be able to do so in the described scenarios because the autofill request is never received.

We will continue to monitor this issue for solutions or workarounds. If anyone has more details they think would be helpful, please feel free to share here.

Side note:
@mcontenti you mentioned..

I was prompted with saved logins on the keyboard, but the password wasn't filled as I tapped one of them:

This is a separate issue we are aware of and are investigating.

<!-- gh-comment-id:3697133983 --> @SaintPatrck commented on GitHub (Dec 29, 2025): Hi all, Thank you for providing logs. Unfortunately the logs indicate Bitwarden did not receive an autofill request in the described failure scenarios. That means Bitwarden has nothing it can evaluate to determine if the request is from an HTTP or HTTPS site to accept or reject it. What's being described, and backed up by the logs, indicates an issue between the website, browser, and/or Android's Autofill service resulting in the autofill request, whether triggered by the site or not, never making it to Bitwarden. For more context; if we wanted to prevent autofilling HTTP sites we would have to evaluate the autofill request metadata, then explicitly reject it. Even if we did perform HTTP filtering (which we DO NOT), we would not be able to do so in the described scenarios because the autofill request is never received. We will continue to monitor this issue for solutions or workarounds. If anyone has more details they think would be helpful, please feel free to share here. Side note: @mcontenti you mentioned.. > I was prompted with saved logins on the keyboard, but the password wasn't filled as I tapped one of them: This is a separate issue we are aware of and are investigating.
GiteaMirror commented 2026-04-18 12:06:53 -05:00
Author
Owner
Copy Link
Copy Source

@Kuhumku commented on GitHub (Dec 30, 2025):

I've also had this issue with android/brave/bitwarden for a while with my self-hosted apps/services that use http (and my logs from bitwarden look the same as the ones shared here). So I've tried experimenting with the flags in brave.

One that seems to have solved it is: "Insecure origins treated as secure" (#unsafely-treat-insecure-origin-as-secure), enabled it, added the domains/IPs I want to use bitwarden on and so far bitwarden has been working again on those http sites.

Now, its only been 2 days since I enabled this flag so if it goes back to not working, I'll comment again

<!-- gh-comment-id:3699168514 --> @Kuhumku commented on GitHub (Dec 30, 2025): I've also had this issue with android/brave/bitwarden for a while with my self-hosted apps/services that use http (and my logs from bitwarden look the same as the ones shared here). So I've tried experimenting with the flags in brave. One that seems to have solved it is: "Insecure origins treated as secure" (#unsafely-treat-insecure-origin-as-secure), enabled it, added the domains/IPs I want to use bitwarden on and so far bitwarden has been working again on those http sites. Now, its only been 2 days since I enabled this flag so if it goes back to not working, I'll comment again
GiteaMirror commented 2026-04-18 12:06:53 -05:00
Author
Owner
Copy Link
Copy Source

@Daniel-PT commented on GitHub (Dec 30, 2025):

I've also had this issue with android/brave/bitwarden for a while with my self-hosted apps/services that use http (and my logs from bitwarden look the same as the ones shared here). So I've tried experimenting with the flags in brave.

One that seems to have solved it is: "Insecure origins treated as secure" (#unsafely-treat-insecure-origin-as-secure), enabled it, added the domains/IPs I want to use bitwarden on and so far bitwarden has been working again on those http sites.

Now, its only been 2 days since I enabled this flag so if it goes back to not working, I'll comment again

Ouh can you meaby tell a little more? Where do you find that option? :)

<!-- gh-comment-id:3700515447 --> @Daniel-PT commented on GitHub (Dec 30, 2025): > I've also had this issue with android/brave/bitwarden for a while with my self-hosted apps/services that use http (and my logs from bitwarden look the same as the ones shared here). So I've tried experimenting with the flags in brave. > > One that seems to have solved it is: "Insecure origins treated as secure" (#unsafely-treat-insecure-origin-as-secure), enabled it, added the domains/IPs I want to use bitwarden on and so far bitwarden has been working again on those http sites. > > Now, its only been 2 days since I enabled this flag so if it goes back to not working, I'll comment again Ouh can you meaby tell a little more? Where do you find that option? :)
GiteaMirror commented 2026-04-18 12:06:54 -05:00
Author
Owner
Copy Link
Copy Source

@Kuhumku commented on GitHub (Dec 30, 2025):

Sure! Its under brave://flags as "Insecure origins treated as secure" and you just add your http sites there, separated by a comma and then relaunch brave.
Some more info from brave's about menu: App version: Brave 1.85.117, Chromium 143.0.7499.146

Image

<!-- gh-comment-id:3700565555 --> @Kuhumku commented on GitHub (Dec 30, 2025): Sure! Its under brave://flags as "Insecure origins treated as secure" and you just add your http sites there, separated by a comma and then relaunch brave. Some more info from brave's about menu: App version: Brave 1.85.117, Chromium 143.0.7499.146 ![Image](https://github.com/user-attachments/assets/7312ee0c-f43b-40ce-bff6-4d702d102232)
GiteaMirror commented 2026-04-18 12:06:54 -05:00
Author
Owner
Copy Link
Copy Source

@Daniel-PT commented on GitHub (Jan 1, 2026):

Sure! Its under brave://flags as "Insecure origins treated as secure" and you just add your http sites there, separated by a comma and then relaunch brave. Some more info from brave's about menu: App version: Brave 1.85.117, Chromium 143.0.7499.146

Image

Wuhu! Thanks it works!

<!-- gh-comment-id:3704036811 --> @Daniel-PT commented on GitHub (Jan 1, 2026): > Sure! Its under brave://flags as "Insecure origins treated as secure" and you just add your http sites there, separated by a comma and then relaunch brave. Some more info from brave's about menu: App version: Brave 1.85.117, Chromium 143.0.7499.146 > > ![Image](https://github.com/user-attachments/assets/7312ee0c-f43b-40ce-bff6-4d702d102232) Wuhu! Thanks it works!
GiteaMirror commented 2026-04-18 12:06:55 -05:00
Author
Owner
Copy Link
Copy Source

@mathisgauthey commented on GitHub (Feb 26, 2026):

The option with insecure URL's doesn't work on my case. I force stopped, reinstalled, uncheck and rechecked all autofill settings, nothing make it want to autofill on Brave using Android 16 on my Pixel 9 Pro.

<!-- gh-comment-id:3967154161 --> @mathisgauthey commented on GitHub (Feb 26, 2026): The option with insecure URL's doesn't work on my case. I force stopped, reinstalled, uncheck and rechecked all autofill settings, nothing make it want to autofill on Brave using Android 16 on my Pixel 9 Pro.
GiteaMirror commented 2026-04-18 12:06:55 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Feb 26, 2026):

nothing make it want to autofill on Brave using Android 16 on my Pixel 9 Pro.

@mathisgauthey Are you talking about autofill on an http site? Or are you talking about autofill in general (i.e. you can't autofill on Brave at all, also not on regular https sites)?

<!-- gh-comment-id:3967237676 --> @pamperer562580892423 commented on GitHub (Feb 26, 2026): > nothing make it want to autofill on Brave using Android 16 on my Pixel 9 Pro. @mathisgauthey Are you talking about autofill on an http site? Or are you talking about autofill in general (i.e. you can't autofill on Brave at all, also not on regular https sites)?
GiteaMirror commented 2026-04-18 12:06:56 -05:00
Author
Owner
Copy Link
Copy Source

@mathisgauthey commented on GitHub (Feb 26, 2026):

nothing make it want to autofill on Brave using Android 16 on my Pixel 9 Pro.

@mathisgauthey Are you talking about autofill on an http site? Or are you talking about autofill in general (i.e. you can't autofill on Brave at all, also not on regular https sites)?

It works fine on apps and on https website.

Just not on http ones like my raspberry pi hosted webapps (be it using raspberry.local or PI_IP-ADDRESS).

The Brave flag for insecure origins has no effect at all on my end.

<!-- gh-comment-id:3967254860 --> @mathisgauthey commented on GitHub (Feb 26, 2026): > > nothing make it want to autofill on Brave using Android 16 on my Pixel 9 Pro. > > @mathisgauthey Are you talking about autofill on an http site? Or are you talking about autofill in general (i.e. you can't autofill on Brave at all, also not on regular https sites)? It works fine on apps and on `https` website. Just not on `http` ones like my raspberry pi hosted webapps (be it using `raspberry.local` or `PI_IP-ADDRESS`). The Brave flag for insecure origins has no effect at all on my end.
GiteaMirror commented 2026-04-18 12:06:56 -05:00
Author
Owner
Copy Link
Copy Source

@Kuhumku commented on GitHub (Feb 26, 2026):

It's still working for me, but I cant speak for Android 16, I'm on Android 13 with an S20.
The only other flag that might have an effect that I have enabled is the one bitwarden recommended: "Android Autofill updates context for WebContents" - #autofill-update-context-for-web-contents.

For BW, everything else in bitwarden is I think the standard, autofill on, use brave autofill integration on, I use base domain as a default. For the login info itself in BW, I always use the http URI: http://192.0.0.0:0000 for example

<!-- gh-comment-id:3967407552 --> @Kuhumku commented on GitHub (Feb 26, 2026): It's still working for me, but I cant speak for Android 16, I'm on Android 13 with an S20. The only other flag that might have an effect that I have enabled is the one bitwarden recommended: "Android Autofill updates context for WebContents" - #autofill-update-context-for-web-contents. For BW, everything else in bitwarden is I think the standard, autofill on, use brave autofill integration on, I use base domain as a default. For the login info itself in BW, I always use the http URI: http://192.0.0.0:0000 for example
GiteaMirror commented 2026-04-18 12:06:57 -05:00
Author
Owner
Copy Link
Copy Source

@mathisgauthey commented on GitHub (Feb 28, 2026):

Hi, for all of you dealing with this issue, and for the time before a fix comes up, I suggest to use the Android Quick Tile Shortcut as support suggested me to try. It works fine. It's bothersome and less fast, but it's a good temporary workaround !

<!-- gh-comment-id:3976583681 --> @mathisgauthey commented on GitHub (Feb 28, 2026): Hi, for all of you dealing with this issue, and for the time before a fix comes up, I suggest to use the [Android Quick Tile Shortcut](https://bitwarden.com/help/auto-fill-android/#quick-action-tiles) as support suggested me to try. It works fine. It's bothersome and less fast, but it's a good temporary workaround !
GiteaMirror commented 2026-04-18 12:06:57 -05:00
Author
Owner
Copy Link
Copy Source

@orlandod543 commented on GitHub (Mar 9, 2026):

I have been dealing with this issue trying to autofill passwords on my local network. The flag "Insecure origins treated as secure" works for me but only if I specify the url:port . Using url alone or URL:* does not autofill

<!-- gh-comment-id:4022010411 --> @orlandod543 commented on GitHub (Mar 9, 2026): I have been dealing with this issue trying to autofill passwords on my local network. The flag "Insecure origins treated as secure" works for me but only if I specify the url:port . Using url alone or URL:* does not autofill
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 labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#28185