[GH-ISSUE #6107] [PM-27708] Autofill regression in multiple browsers: Bitwarden 2025.10.1 stops matching by website domain and falls back to package name (e.g. com.sec.android.app.sbrowser) #8403

New Issue

GiteaMirror · 2026-04-11T01:40:36-05:00

GiteaMirror commented

2026-04-11 01:40:36 -05:00

Originally created by @rallyemax on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6107

Steps To Reproduce

Open ~~Samsung Internet~~ a Chromium-based browser other than Chrome itself (e.g. Samsung Browser, Edge) and navigate to any login form (example: https://authenticationtest.com)
Tap into the username or password input field.
Enter the Bitwarden vault (ignore suggestions) when prompted.

Expected Result

Bitwarden should match the login item by the website’s domain (e.g., authenticationtest.com) and show entries where that domain is listed as a URI.

Actual Result

Bitwarden instead shows items only for the browser package name (for Samsung Browser, it is androidapp://com.sec.android.app.sbrowser) as if no website domain were available.

Screenshots or Videos

No response

Additional Context

Android Autofill does provide the correct page domain to the autofill session, as confirmed by the following snippets from logcat and dumpsys autofill:

AssistStructure: Web domain: authenticationtest.com
AutofillSession: Setting urlBar ... domain authenticationtest.com

Login field nodes with credential hints and the URL bar node are both present in the same AssistStructure tree.

Chrome’s AssistStructure has a similar “domain on one node, username/password hints on another” layout — but Chrome is matched successfully in both 2025.10.0 and 2025.10.1.

Therefore the regression appears to be in Bitwarden’s association logic that maps focused credential fields to the extracted mUrlBar domain specifically in Samsung Internet’s structure.

This is a domain association regression introduced in 2025.10.1, affecting Samsung Internet autofill flows. Rolling back to 2025.10.0 restores correct behavior.

Workaround

Until Bitwarden is updated with a fix, consider downgrading to version 2025.10.0, which resolves this issue completely.

Build Version

2025.10.1

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Device: Samsung Galaxy S25
OS: Android 16 / OneUI 8.0

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.

Edited 13 Nov 2025 to include other Chromium-based browsers and emphasize the suggested workaround in its own section

Originally created by @rallyemax on GitHub (Oct 31, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6107 ### Steps To Reproduce 1. Open ~~Samsung Internet~~ a Chromium-based browser other than Chrome itself (e.g. Samsung Browser, Edge) and navigate to any login form (example: https://authenticationtest.com) 2. Tap into the username or password input field. 3. Enter the Bitwarden vault (ignore suggestions) when prompted. ### Expected Result Bitwarden should match the login item by the website’s domain (e.g., authenticationtest.com) and show entries where that domain is listed as a URI. ### Actual Result Bitwarden instead shows items only for the browser package name (for Samsung Browser, it is `androidapp://com.sec.android.app.sbrowser`) as if no website domain were available. ### Screenshots or Videos _No response_ ### Additional Context Android Autofill does provide the correct page domain to the autofill session, as confirmed by the following snippets from `logcat` and `dumpsys autofill`: > AssistStructure: Web domain: authenticationtest.com AutofillSession: Setting urlBar ... domain authenticationtest.com Login field nodes with credential hints and the URL bar node are both present in the same AssistStructure tree. Chrome’s AssistStructure has a similar “domain on one node, username/password hints on another” layout — but Chrome is matched successfully in both 2025.10.0 and 2025.10.1. Therefore the regression appears to be in Bitwarden’s association logic that maps focused credential fields to the extracted mUrlBar domain specifically in Samsung Internet’s structure. This is a domain association regression introduced in 2025.10.1, affecting Samsung Internet autofill flows. Rolling back to 2025.10.0 restores correct behavior. ### Workaround Until Bitwarden is updated with a fix, consider downgrading to version 2025.10.0, which resolves this issue completely. ### Build Version 2025.10.1 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Samsung Galaxy S25 - OS: Android 16 / OneUI 8.0 ### 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. _Edited 13 Nov 2025 to include other Chromium-based browsers and emphasize the suggested workaround in its own section_

GiteaMirror added the app:password-manager bug labels 2026-04-11 01:40:36 -05:00

GiteaMirror closed this issue

2026-04-11 01:40:36 -05:00

GiteaMirror commented

2026-04-11 01:40:38 -05:00

@bitwarden-bot commented on GitHub (Oct 31, 2025):

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

@bitwarden-bot commented on GitHub (Oct 31, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-27708

GiteaMirror commented

2026-04-11 01:40:39 -05:00

@rallyemax commented on GitHub (Oct 31, 2025):

I'm not really in a position to bisect the recent commits, but if I had to guess, I would guess that the regression came in via https://github.com/bitwarden/android/pull/5977.

That commit changed the AssistStructure parsing logic. When comparing the AssistStructures coming out of Samsung Internet and Chrome, they do appear to be structured somewhat differently. That difference might be enough to trigger the app URI fallback in the case of Samsung Internet, whereas the Chrome case stays on the happy path and doesn't fall through.

@rallyemax commented on GitHub (Oct 31, 2025): I'm not really in a position to bisect the recent commits, but if I had to guess, I would guess that the regression came in via https://github.com/bitwarden/android/pull/5977. That commit changed the AssistStructure parsing logic. When comparing the AssistStructures coming out of Samsung Internet and Chrome, they do appear to be structured somewhat differently. That difference might be enough to trigger the app URI fallback in the case of Samsung Internet, whereas the Chrome case stays on the happy path and doesn't fall through.

GiteaMirror commented

2026-04-11 01:40:39 -05:00

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

This problem has also occurred in the edge browser. The website can't be filled normally, only the application package name of edge pops up.Rolling back the last version of bitwarden can be filled normally.
@bitwarden-bot

@Chaniug commented on GitHub (Nov 1, 2025): This problem has also occurred in the edge browser. The website can't be filled normally, only the application package name of edge pops up.Rolling back the last version of bitwarden can be filled normally. @bitwarden-bot

GiteaMirror commented

2026-04-11 01:40:39 -05:00

@byteme4188 commented on GitHub (Nov 2, 2025):

This also happens in edge. Edge defaults to com.microsoft.emmx for all domains. Tested on my pixel 9 pro xl and also galaxy s24 ultra

@byteme4188 commented on GitHub (Nov 2, 2025): This also happens in edge. Edge defaults to com.microsoft.emmx for all domains. Tested on my pixel 9 pro xl and also galaxy s24 ultra

GiteaMirror commented

2026-04-11 01:40:39 -05:00

@kreativekrise commented on GitHub (Nov 2, 2025):

I can confirm that it stopped working on Edge. Tested on Google Pixel 9 Pro. A downgrade from 2025.10.1 to 2025.10.0 solved the issue.

@kreativekrise commented on GitHub (Nov 2, 2025): I can confirm that it stopped working on Edge. Tested on Google Pixel 9 Pro. A downgrade from 2025.10.1 to 2025.10.0 solved the issue.

GiteaMirror commented

2026-04-11 01:40:40 -05:00

@ddejan75 commented on GitHub (Nov 3, 2025):

Also I can confirme that it stopped working in Edge on Samsung S24, downgraded as well.

@ddejan75 commented on GitHub (Nov 3, 2025): Also I can confirme that it stopped working in Edge on Samsung S24, downgraded as well.

GiteaMirror commented

2026-04-11 01:40:41 -05:00

@YamenSharaf commented on GitHub (Nov 3, 2025):

Same here on S25 and Edge.

Anyway to downgrade without uninstalling?

@YamenSharaf commented on GitHub (Nov 3, 2025): Same here on S25 and Edge. Anyway to downgrade without uninstalling?

GiteaMirror commented

2026-04-11 01:40:41 -05:00

@jtodddd commented on GitHub (Nov 3, 2025):

Hi there,

This report has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@jtodddd commented on GitHub (Nov 3, 2025): Hi there, This report has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!

GiteaMirror commented

2026-04-11 01:40:41 -05:00

@lexcyn commented on GitHub (Nov 5, 2025):

Same happening here on Samsung S25 Ultra for any Chromium based browser

@lexcyn commented on GitHub (Nov 5, 2025): Same happening here on Samsung S25 Ultra for any Chromium based browser

GiteaMirror commented

2026-04-11 01:40:42 -05:00

@twjazzhuang commented on GitHub (Nov 5, 2025):

I am experiencing the same problem on my POCO F5 with Xiaomi HyperOS 2.0.210.0 using Edge browser. Bitwarden is only matching on the Edge browser app package (com.microsoft.emmx) instead of the website domain, making autofill unusable on web pages. Downgrading Bitwarden to the previous version restores autofill functionality. Please investigate compatibility for Edge on HyperOS.

@twjazzhuang commented on GitHub (Nov 5, 2025): I am experiencing the same problem on my POCO F5 with Xiaomi HyperOS 2.0.210.0 using Edge browser. Bitwarden is only matching on the Edge browser app package (com.microsoft.emmx) instead of the website domain, making autofill unusable on web pages. Downgrading Bitwarden to the previous version restores autofill functionality. Please investigate compatibility for Edge on HyperOS.

GiteaMirror commented

2026-04-11 01:40:43 -05:00

@rouxsean commented on GitHub (Nov 5, 2025):

EDIT: Rolled back to 10.0 (20794) and autofill is working properly on Samsung Internet (using URL as expected instead of the Samsung Internet package name). Leads me to believe it's a Bitwarden issue ;)

Thank you @Chaniug & @KreativeKrise !

Came to report the same exact thing:

Autofill pop-ups are working on the Samsung Internet app, but when they are clicked on, Bitwarden is using the Samsung Internet package name instead of the website: com.sec.android.app.sbrowser

I have uninstalled, rebooted, reinstalled Bitwarden. Toggled autofill settings (including not using Bitwarden to autofill, chrome autofill integration, accessibility toggle, etc.)

Using Samsung Galaxy Z Fold 6, Bitwarden Version 2025.10.1(20867), Samsung Internet 29.0.0.59, One UI 8, Android 16.

This started happing a little under a week ago, after an app launched a pop-up for authentication with Google. (Samsung Internet is default browser). This may be coincident timing.

I haven't found other posts about this (reddit, etc.), so wasn't sure if this is a known issue. So here I am.

Thank you to the devs for looking into this as it seems others are having similar issues.

Chrome works properly as expected, with autofill suggestions coming from the URL (not the chrome package name).

@rouxsean commented on GitHub (Nov 5, 2025): EDIT: Rolled back to 10.0 (20794) and autofill is working properly on Samsung Internet (using URL as expected instead of the Samsung Internet package name). Leads me to believe it's a Bitwarden issue ;) Thank you @Chaniug & @KreativeKrise ! ---------------- Came to report the same exact thing: Autofill pop-ups are working on the Samsung Internet app, but when they are clicked on, Bitwarden is using the Samsung Internet package name instead of the website: com.sec.android.app.sbrowser I have uninstalled, rebooted, reinstalled Bitwarden. Toggled autofill settings (including not using Bitwarden to autofill, chrome autofill integration, accessibility toggle, etc.) Using Samsung Galaxy Z Fold 6, Bitwarden Version 2025.10.1(20867), Samsung Internet 29.0.0.59, One UI 8, Android 16. This started happing a little under a week ago, after an app launched a pop-up for authentication with Google. (Samsung Internet is default browser). This may be coincident timing. I haven't found other posts about this (reddit, etc.), so wasn't sure if this is a known issue. So here I am. Thank you to the devs for looking into this as it seems others are having similar issues. Chrome works properly as expected, with autofill suggestions coming from the URL (not the chrome package name).

GiteaMirror commented

2026-04-11 01:40:43 -05:00

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

Same on brave and brave nightly version.
Pixel 9 pro XL

@Kazenn commented on GitHub (Nov 6, 2025): Same on brave and brave nightly version. Pixel 9 pro XL

GiteaMirror commented

2026-04-11 01:40:43 -05:00

@diogodh commented on GitHub (Nov 6, 2025):

Happens to me as well with latest bitwarden app on Android 16 on pixel 8 and edge browser

@diogodh commented on GitHub (Nov 6, 2025): Happens to me as well with latest bitwarden app on Android 16 on pixel 8 and edge browser

GiteaMirror commented

2026-04-11 01:40:44 -05:00

@servint commented on GitHub (Nov 6, 2025):

On Android 16 with the Samsung S23+ and the latest version of the Edge browser, the app detects the package name instead of the web page. If you're on a page and tap an input element, Bitwarden suggests filling in for the Edge package name. However, if you tap the Bitwarden autofill icon in the notification panel, it correctly shows the autofill suggestion for the page.

@servint commented on GitHub (Nov 6, 2025): On Android 16 with the Samsung S23+ and the latest version of the Edge browser, the app detects the package name instead of the web page. If you're on a page and tap an input element, Bitwarden suggests filling in for the Edge package name. However, if you tap the Bitwarden autofill icon in the notification panel, it correctly shows the autofill suggestion for the page.

GiteaMirror commented

2026-04-11 01:40:45 -05:00

@Faustpfand commented on GitHub (Nov 6, 2025):

Pixel 9 Pro
Android 16 - BP3A.251005.004.B3
Microsoft Edge 141.0.3537.99
Bitwarden 2025.10.1

Same problem

@Faustpfand commented on GitHub (Nov 6, 2025): Pixel 9 Pro Android 16 - BP3A.251005.004.B3 Microsoft Edge 141.0.3537.99 Bitwarden 2025.10.1 Same problem

GiteaMirror commented

2026-04-11 01:40:45 -05:00

@Melantrix commented on GitHub (Nov 6, 2025):

Nothing phone 2
Android 15 with september 2025 update
Bitwarden 2025.10.1

Same issue

@Melantrix commented on GitHub (Nov 6, 2025): Nothing phone 2 Android 15 with september 2025 update Bitwarden 2025.10.1 Same issue

GiteaMirror commented

2026-04-11 01:40:46 -05:00

@ExRazor commented on GitHub (Nov 6, 2025):

Same issue on my Xiaomi Poco F6 with Edge Browser.
Hopefully it will get fixed soon...

@ExRazor commented on GitHub (Nov 6, 2025): Same issue on my Xiaomi Poco F6 with Edge Browser. Hopefully it will get fixed soon...

GiteaMirror commented

2026-04-11 01:40:46 -05:00

@DorianDescamps commented on GitHub (Nov 7, 2025):

Same issue here 😣
Galaxy S24 Ultra
Android 16 september update
Bitwarden 2025.10.1

Temporary fixed with rollback f-droid 2025.10.0

@DorianDescamps commented on GitHub (Nov 7, 2025): Same issue here 😣 Galaxy S24 Ultra Android 16 september update Bitwarden 2025.10.1 Temporary fixed with rollback f-droid 2025.10.0

GiteaMirror commented

2026-04-11 01:40:47 -05:00

@sargeZam commented on GitHub (Nov 7, 2025):

Same issue here.

Galaxy S25, Android 16 with the latest update. It happens with Samsung Internet, Edge, or Vivaldi. It still works fine with Chrome.

@sargeZam commented on GitHub (Nov 7, 2025): Same issue here. Galaxy S25, Android 16 with the latest update. It happens with Samsung Internet, Edge, or Vivaldi. It still works fine with Chrome.

GiteaMirror commented

2026-04-11 01:40:48 -05:00

@astoyanovgh commented on GitHub (Nov 7, 2025):

Same issue on updated Pixel 9 pro. No problem with kiwi browser, same issue with Samsung Internet

@astoyanovgh commented on GitHub (Nov 7, 2025): Same issue on updated Pixel 9 pro. No problem with kiwi browser, same issue with Samsung Internet

GiteaMirror commented

2026-04-11 01:40:49 -05:00

@androidacy-user commented on GitHub (Nov 8, 2025):

Same on edge 142. The "improved chrome security" is to blame I'm guessing

@androidacy-user commented on GitHub (Nov 8, 2025): Same on edge 142. The "improved chrome security" is to blame I'm guessing

GiteaMirror commented

2026-04-11 01:40:51 -05:00

@Bori94 commented on GitHub (Nov 8, 2025):

Having the same issue for a few days now. Using Edge on Samsung S24 Ultra Android 16 One UI 8.0

@Bori94 commented on GitHub (Nov 8, 2025): Having the same issue for a few days now. Using Edge on Samsung S24 Ultra Android 16 One UI 8.0

GiteaMirror commented

2026-04-11 01:40:54 -05:00

@zzahkaboom24 commented on GitHub (Nov 8, 2025):

Can confirm Bitwarden 2025.10.1 being the issue.
Downgrading to 2025.10.0 fixes it for me for Microsoft Edge, and shows the login URL properly.

@zzahkaboom24 commented on GitHub (Nov 8, 2025): Can confirm Bitwarden 2025.10.1 being the issue. Downgrading to 2025.10.0 fixes it for me for Microsoft Edge, and shows the login URL properly.

GiteaMirror commented

2026-04-11 01:40:55 -05:00

@HoodFeelGood commented on GitHub (Nov 8, 2025):

I can confirm this started happening on Edge for Android a few days ago.

@HoodFeelGood commented on GitHub (Nov 8, 2025): I can confirm this started happening on Edge for Android a few days ago.

GiteaMirror commented

2026-04-11 01:40:56 -05:00

@wsinned commented on GitHub (Nov 8, 2025):

Pixel 9a and Edge has the same issue

@wsinned commented on GitHub (Nov 8, 2025): Pixel 9a and Edge has the same issue

GiteaMirror commented

2026-04-11 01:40:57 -05:00

@androidacy-user commented on GitHub (Nov 8, 2025):

Hi there,

This report has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

Anything new? Obviously affecting a lot of people and it basically makes bitwarden useless for anyone not using very modern chrome specifically.

@androidacy-user commented on GitHub (Nov 8, 2025): > Hi there, > > This report has been escalated for further investigation. If you have more information that can help us, please add it below. > > Thanks! Anything new? Obviously affecting a lot of people and it basically makes bitwarden useless for anyone not using very modern chrome specifically.

GiteaMirror commented

2026-04-11 01:40:57 -05:00

@niculicchio commented on GitHub (Nov 8, 2025):

Hi there,
This report has been escalated for further investigation. If you have more information that can help us, please add it below.
Thanks!

Anything new? Obviously affecting a lot of people and it basically makes bitwarden useless for anyone not using very modern chrome specifically.

I agree. And you can't spend a week fixing such a big bug. That's not acceptable from a company like Bitwarden.

@niculicchio commented on GitHub (Nov 8, 2025): > > Hi there, > > This report has been escalated for further investigation. If you have more information that can help us, please add it below. > > Thanks! > > Anything new? Obviously affecting a lot of people and it basically makes bitwarden useless for anyone not using very modern chrome specifically. I agree. And you can't spend a week fixing such a big bug. That's not acceptable from a company like Bitwarden.

GiteaMirror commented

2026-04-11 01:40:58 -05:00

@iqlogic commented on GitHub (Nov 8, 2025):

Same on Xiaomi 15 with HyperOS 3.0.4 (Android 16) and Xiaomi Pad 5 with HyperOS 1.0.6 (Android 13). Please fix it asap guys🙏

@iqlogic commented on GitHub (Nov 8, 2025): Same on Xiaomi 15 with HyperOS 3.0.4 (Android 16) and Xiaomi Pad 5 with HyperOS 1.0.6 (Android 13). Please fix it asap guys🙏

GiteaMirror commented

2026-04-11 01:40:59 -05:00

@JoshMart commented on GitHub (Nov 8, 2025):

Same issue on S25 using Samsung Internet 29.0.0.59 and Bitwarden Version: 2025.10.1 (20867)
📱 samsung SM-S931U1 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2025.10-rc37@74b9a12e19e07b60271a1141d3a95f7919811ea4
💻 build source: bitwarden/android/actions/runs/18598736732/attempts/1
🦀 SDK: 1.0.0-3430-fc75b903
🌩 Server: 2025.10.2 @ US

I can clearly see the Samsung Internet package name being used to perform the match instead the website URL.

@JoshMart commented on GitHub (Nov 8, 2025): Same issue on S25 using Samsung Internet 29.0.0.59 and Bitwarden Version: 2025.10.1 (20867) 📱 samsung SM-S931U1 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2025.10-rc37@74b9a12e19e07b60271a1141d3a95f7919811ea4 💻 build source: bitwarden/android/actions/runs/18598736732/attempts/1 🦀 SDK: 1.0.0-3430-fc75b903 🌩 Server: 2025.10.2 @ US I can clearly see the Samsung Internet package name being used to perform the match instead the website URL.

GiteaMirror commented

2026-04-11 01:41:00 -05:00

@MalarKeY007 commented on GitHub (Nov 8, 2025):

S24 Ultra Samsung Internet.

I think this bug requires immediate attention. Given the widespread impact on a significant portion of Bitwarde user base and its effect on core usability, I believe this issue should be prioritized with the highest urgency. It is concerning to pay for a premium service and then have to wait an extended period for a simple bug to fix.

I'm not going to uninstall, to rollback and reconfigure everything again.

@MalarKeY007 commented on GitHub (Nov 8, 2025): S24 Ultra Samsung Internet. I think this bug requires immediate attention. Given the widespread impact on a significant portion of Bitwarde user base and its effect on core usability, I believe this issue should be prioritized with the highest urgency. It is concerning to pay for a premium service and then have to wait an extended period for a simple bug to fix. I'm not going to uninstall, to rollback and reconfigure everything again.

GiteaMirror commented

2026-04-11 01:41:01 -05:00

@androidacy-user commented on GitHub (Nov 9, 2025):

People coming in: please hit the "👍" on the OP instead of posting "me too" type comments. If you have additional insights to share, great, but otherwise you're just spamming the devs and everyone's notifications unnecessarily

@androidacy-user commented on GitHub (Nov 9, 2025): **People coming in: please hit the "👍" on the OP instead of posting "me too" type comments. If you have additional insights to share, great, but otherwise you're just spamming the devs and everyone's notifications unnecessarily**

GiteaMirror commented

2026-04-11 01:41:02 -05:00

@johnfromstatefarm commented on GitHub (Nov 12, 2025):

Shouldn't making a post bump this? Same issue for me on a Z Fold 6.

@johnfromstatefarm commented on GitHub (Nov 12, 2025): Shouldn't making a post bump this? Same issue for me on a Z Fold 6.

GiteaMirror commented

2026-04-11 01:41:03 -05:00

@LorenDB commented on GitHub (Nov 12, 2025):

Also happens on Opera.

@LorenDB commented on GitHub (Nov 12, 2025): Also happens on Opera.

GiteaMirror commented

2026-04-11 01:41:04 -05:00

@scebbers commented on GitHub (Nov 12, 2025):

Same issue on a POCO X6 Pro runing Android 15.

@scebbers commented on GitHub (Nov 12, 2025): Same issue on a POCO X6 Pro runing Android 15.

GiteaMirror commented

2026-04-11 01:41:05 -05:00

@SaintPatrck commented on GitHub (Nov 12, 2025):

Hi all,

The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (#5977) that caused unexpected challenges with those specific browsers. The team has identified the issue and are looking at options to resolve. There is no date available for a fix at this time. Mobile Chrome, Brave, and Firefox are unaffected.

@SaintPatrck commented on GitHub (Nov 12, 2025): Hi all, The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (#5977) that caused unexpected challenges with those specific browsers. The team has identified the issue and are looking at options to resolve. There is no date available for a fix at this time. Mobile Chrome, Brave, and Firefox are unaffected.

GiteaMirror commented

2026-04-11 01:41:06 -05:00

@androidacy-user commented on GitHub (Nov 12, 2025):

Hi all,

The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (#5977) that caused unexpected challenges with those specific browsers. The team has identified the issue and are looking at options to resolve. There is no date available for a fix at this time. Mobile Chrome, Brave, and Firefox are unaffected.

I don't think it's unreasonable to suggest reverting that and doing it properly, especially as that's a non insignificant share of mobile browsers - heck Samsung Internet is the default on OneUI

@androidacy-user commented on GitHub (Nov 12, 2025): > Hi all, > > The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (#5977) that caused unexpected challenges with those specific browsers. The team has identified the issue and are looking at options to resolve. There is no date available for a fix at this time. Mobile Chrome, Brave, and Firefox are unaffected. I don't think it's unreasonable to suggest reverting that and doing it properly, especially as that's a non insignificant share of mobile browsers - heck Samsung Internet is the default on OneUI

GiteaMirror commented

2026-04-11 01:41:07 -05:00

@ahbanavi commented on GitHub (Nov 12, 2025):

Same here.

Android 16
Samsung Galaxy S24
But in Microsoft Edge

All autofill suggestions are using the Microsoft Edge package name instead of the domain.

@ahbanavi commented on GitHub (Nov 12, 2025): Same here. Android 16 Samsung Galaxy S24 But in Microsoft Edge All autofill suggestions are using the Microsoft Edge package name instead of the domain.

GiteaMirror commented

2026-04-11 01:41:07 -05:00

@HoodFeelGood commented on GitHub (Nov 13, 2025):

Agree with reverting back immediately. Not to be hyperbolic, but the number one goal has to be keeping a business-grade paid app in a usable state 99.999%, and right now it isn't in a usable state for anyone with these affected browsers.

@HoodFeelGood commented on GitHub (Nov 13, 2025): Agree with reverting back immediately. Not to be hyperbolic, but the number one goal has to be keeping a business-grade paid app in a usable state 99.999%, and right now it isn't in a usable state for anyone with these affected browsers.

GiteaMirror commented

2026-04-11 01:41:08 -05:00

@snargledorf commented on GitHub (Nov 14, 2025):

Also affected:

Pixel 9 Pro
Android 16 BP3A.251105.015
Microsoft Edge Browser 142.0.3595.66
Bitwarden 2025.10.1

@snargledorf commented on GitHub (Nov 14, 2025): Also affected: Pixel 9 Pro Android 16 BP3A.251105.015 Microsoft Edge Browser 142.0.3595.66 Bitwarden 2025.10.1

GiteaMirror commented

2026-04-11 01:41:09 -05:00

@JayX83 commented on GitHub (Nov 15, 2025):

Any ETA on when we should expect this bug to be fixed? It’s been going on for more than 2 weeks now…

@JayX83 commented on GitHub (Nov 15, 2025): Any ETA on when we should expect this bug to be fixed? It’s been going on for more than 2 weeks now…

GiteaMirror commented

2026-04-11 01:41:10 -05:00

@alien75 commented on GitHub (Nov 15, 2025):

Same with Samsung Internet Browser on S25 Plus, I had to revert to 2025.10.0 with apk mirror installer.

@alien75 commented on GitHub (Nov 15, 2025): Same with Samsung Internet Browser on S25 Plus, I had to revert to 2025.10.0 with apk mirror installer.

GiteaMirror commented

2026-04-11 01:41:10 -05:00

@MartinDoms commented on GitHub (Nov 15, 2025):

The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (https://github.com/bitwarden/android/pull/5977) that caused unexpected challenges with those specific browsers.

That PR affects 23 files, more than 260 lines of code changed, and the review was approved 6 minutes after being marked Ready for Review. This does not indicate a serious level of oversight. It has now caused a bug that is making the app unusable in browsers for a large proportion of your userbase.

Given the state of autofill in Android I would hope that changes that tighten it up even further would receive more oversight in the future.

@MartinDoms commented on GitHub (Nov 15, 2025): > The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (https://github.com/bitwarden/android/pull/5977) that caused unexpected challenges with those specific browsers. That PR affects 23 files, more than 260 lines of code changed, and the review was approved 6 minutes after being marked Ready for Review. This does not indicate a serious level of oversight. It has now caused a bug that is making the app unusable in browsers for a large proportion of your userbase. Given the state of autofill in Android I would hope that changes that tighten it up even further would receive more oversight in the future.

GiteaMirror commented

2026-04-11 01:41:10 -05:00

@androidacy-user commented on GitHub (Nov 15, 2025):

Brave Beta is also affected by this issue.
Device OnePlus 13 with Android 15 and Android 16.

Switch to " autofill with third party " in settings. The change primarily negatively affects browsers that haven't implemented that

@androidacy-user commented on GitHub (Nov 15, 2025): > Brave Beta is also affected by this issue. > Device OnePlus 13 with Android 15 and Android 16. Switch to " autofill with third party " in settings. The change primarily negatively affects browsers that haven't implemented that

GiteaMirror commented

2026-04-11 01:41:11 -05:00

@jjsmackay commented on GitHub (Nov 16, 2025):

I have been advocating for our company to switch to bitwarden but now wear pie on my face as a result of this regression.

I note there is no mention of this on the troubleshooting help page linked from the app settings:

Having trouble with autofill?
Access help and troubleshooting documentation here

Not a good look team.

@jjsmackay commented on GitHub (Nov 16, 2025): I have been advocating for our company to switch to bitwarden but now wear pie on my face as a result of this regression. I note there is no mention of this on the troubleshooting help page linked from the app settings: > Having trouble with autofill? > Access help and troubleshooting documentation [here](https://bitwarden.com/help/auto-fill-android-troubleshooting/) Not a good look team.

GiteaMirror commented

2026-04-11 01:41:12 -05:00

@Toriigate commented on GitHub (Nov 16, 2025):

A critical bug that is making the app unusable for a significant chunk of users, and it's now been over two weeks without fix... 🤦‍♂️

@Toriigate commented on GitHub (Nov 16, 2025): A critical bug that is making the app unusable for a significant chunk of users, and it's now been over two weeks without fix... 🤦‍♂️

GiteaMirror commented

2026-04-11 01:41:13 -05:00

@johnfromstatefarm commented on GitHub (Nov 16, 2025):

I wonder why the dev team is struggling so much to just remove the line of code that broke this. It shouldn't take 2 weeks.

@johnfromstatefarm commented on GitHub (Nov 16, 2025): I wonder why the dev team is struggling so much to just remove the line of code that broke this. It shouldn't take 2 weeks.

GiteaMirror commented

2026-04-11 01:41:13 -05:00

@yunshouhu commented on GitHub (Nov 16, 2025):

您好，邮件我已经收到，我会尽快给您回复。祝你学习进步，工作顺利！

@yunshouhu commented on GitHub (Nov 16, 2025): 您好，邮件我已经收到，我会尽快给您回复。祝你学习进步，工作顺利！

GiteaMirror commented

2026-04-11 01:41:14 -05:00

@gaiking-uk commented on GitHub (Nov 16, 2025):

I am also affected but am not sure how to downgrade to 2025.10.0

I uninstalled the 2025.10.1 version from the Google Play Store and thought I could manually download and install the .APK files from the 2025.10.0 release, but neither the plain/fdroid versions work...

Am I missing something?

EDIT: OK, turns out it was an issue with my device as I use a Knox work profile, which also has BitWarden running on it... I did tap "uninstall for all users" but this didn't seem to work as was still installed on work profile, which was then causing an issue when I tried to install the APK.

@gaiking-uk commented on GitHub (Nov 16, 2025): I am also affected but am not sure how to downgrade to 2025.10.0 I uninstalled the 2025.10.1 version from the Google Play Store and thought I could manually download and install the .APK files from the 2025.10.0 release, but neither the plain/fdroid versions work... ![Image](https://github.com/user-attachments/assets/ef839891-c69d-482d-b8a7-7bb548606a73) Am I missing something? *** **EDIT**: OK, turns out it was an issue with my device as I use a Knox work profile, which also has BitWarden running on it... I did tap "uninstall for all users" but this didn't seem to work as was still installed on work profile, which was then causing an issue when I tried to install the APK.

GiteaMirror commented

2026-04-11 01:41:14 -05:00

@alien75 commented on GitHub (Nov 16, 2025):

Am I missing something?

I downloaded v2025.10.0 package from apk mirror and installed with their app

@alien75 commented on GitHub (Nov 16, 2025): > Am I missing something? I downloaded v2025.10.0 package from apk mirror and installed with their app

GiteaMirror commented

2026-04-11 01:41:15 -05:00

@gaiking-uk commented on GitHub (Nov 16, 2025):

I downloaded v2025.10.0 package from apk mirror and installed with their app

Thanks @alien75, I was able to get the install working in the end (turned out to be an issue with my device)... Also wanted to follow-up on APK Mirror though as while I don't have any issues with them generally (I have used them myself previously), but just thought you might want to reconsider installing the official APK file from BitWarden's github - given how critical it is for managing all your other accounts/passwords(?) 🤔

@gaiking-uk commented on GitHub (Nov 16, 2025): > I downloaded v2025.10.0 package from apk mirror and installed with their app Thanks @alien75, I was able to get the install working in the end (turned out to be an issue with my device)... Also wanted to follow-up on APK Mirror though as while I don't have any issues with them generally (I have used them myself previously), but just thought you might want to reconsider installing the [official APK file from BitWarden's github](https://github.com/bitwarden/android/releases/download/v2025.10.0-bwpm/com.x8bit.bitwarden.apk) - given how critical it is for managing all your other accounts/passwords(?) 🤔

GiteaMirror commented

2026-04-11 01:41:15 -05:00

@alien75 commented on GitHub (Nov 16, 2025):

I downloaded v2025.10.0 package from apk mirror and installed with their app

Thanks @alien75, I was able to get the install working in the end (turned out to be an issue with my device)... Also wanted to follow-up on APK Mirror though as while I don't have any issues with them generally (I have used them myself previously), but just thought you might want to reconsider installing the official APK file from BitWarden's github - given how critical it is for managing all your other accounts/passwords(?) 🤔

Thanks for the advice, I just downloaded official apk and installed over the one from apkmirror. Before the apk mirror version I was not able to install the official, don't know why.

@alien75 commented on GitHub (Nov 16, 2025): > > I downloaded v2025.10.0 package from apk mirror and installed with their app > > Thanks [@alien75](https://github.com/alien75), I was able to get the install working in the end (turned out to be an issue with my device)... Also wanted to follow-up on APK Mirror though as while I don't have any issues with them generally (I have used them myself previously), but just thought you might want to reconsider installing the [official APK file from BitWarden's github](https://github.com/bitwarden/android/releases/download/v2025.10.0-bwpm/com.x8bit.bitwarden.apk) - given how critical it is for managing all your other accounts/passwords(?) 🤔 Thanks for the advice, I just downloaded official apk and installed over the one from apkmirror. Before the apk mirror version I was not able to install the official, don't know why.

GiteaMirror commented

2026-04-11 01:41:16 -05:00

@diamant-x commented on GitHub (Nov 17, 2025):

Facing same issue here With Android Bitwarden 2025.10.1 (20867) and Microsoft Edge 142.0.3595.66 and Android 15.
I realized Edge in mobile now offers the option to install extensions, Bitwarden among them.

Would in any way that be the recommended way for auto-fill now within Edge?

https://edgestatic.azureedge.net/shared/cms/lrs1c69a1j/section-images/5d92c92fdf1045d5830e023cd72ddb80-png-w1823.avif

@diamant-x commented on GitHub (Nov 17, 2025): Facing same issue here With Android Bitwarden 2025.10.1 (20867) and Microsoft Edge 142.0.3595.66 and Android 15. I realized Edge in mobile now offers the option to install extensions, Bitwarden among them. - Would in any way that be the recommended way for auto-fill now within Edge? https://edgestatic.azureedge.net/shared/cms/lrs1c69a1j/section-images/5d92c92fdf1045d5830e023cd72ddb80-png-w1823.avif

GiteaMirror commented

2026-04-11 01:41:17 -05:00

@ccMatrix commented on GitHub (Nov 17, 2025):

I have Bitwarden as a quick setting button and while the normal autofill currently doesn't work for brwosers, opening Bitwarden from the quick setting button does show the correct vault entries for the website.

@ccMatrix commented on GitHub (Nov 17, 2025): I have Bitwarden as a quick setting button and while the normal autofill currently doesn't work for brwosers, opening Bitwarden from the quick setting button does show the correct vault entries for the website.

GiteaMirror commented

2026-04-11 01:41:17 -05:00

@seekified commented on GitHub (Nov 17, 2025):

The "me too" comments are not helping and are just generating spam for the people subscribed to this issue. Bitwarden are aware that this is fucked. They need to fix it ASAP. That's all.

@seekified commented on GitHub (Nov 17, 2025): The "me too" comments are not helping and are just generating spam for the people subscribed to this issue. Bitwarden are aware that this is fucked. They need to fix it ASAP. That's all.

GiteaMirror commented

2026-04-11 01:41:18 -05:00

@david-livefront commented on GitHub (Nov 17, 2025):

This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers.

There is also a separate issue with the latest version of Samsung Internet Browser (v29.x.x.x) that has broken compatibility with Autofill on older versions of the Android OS. This issue is something that needs to be handled by the browser developers.

@david-livefront commented on GitHub (Nov 17, 2025): This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers. There is also a separate issue with the latest version of Samsung Internet Browser (v29.x.x.x) that has broken compatibility with Autofill on older versions of the Android OS. This issue is something that needs to be handled by the browser developers.

GiteaMirror commented

2026-04-11 01:41:18 -05:00

@rallyemax commented on GitHub (Nov 18, 2025):

This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers.

There is also a separate issue with the latest version of Samsung Internet Browser (v29.x.x.x) that has broken compatibility with Autofill on older versions of the Android OS. This issue is something that needs to be handled by the browser developers.

Can you provide any additional details about the Android-side changes to autofill that PR #5977 was meant to implement? The commit message doesn't provide much information. Were those Android changes implemented with a go-live date separate from the usual API-level compatibility mechanism?

It sort of felt like the code changes introduced by PR #5977 merely broke the Bitwarden-side heuristics that are used to resolve the AssistStructure data for certain browsers, but I'm happy for that conjecture to be wrong and to learn something.

@rallyemax commented on GitHub (Nov 18, 2025): > This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers. > > There is also a separate issue with the latest version of Samsung Internet Browser (v29.x.x.x) that has broken compatibility with Autofill on older versions of the Android OS. This issue is something that needs to be handled by the browser developers. Can you provide any additional details about the Android-side changes to autofill that PR #5977 was meant to implement? The commit message doesn't provide much information. Were those Android changes implemented with a go-live date separate from the usual API-level compatibility mechanism? It sort of felt like the code changes introduced by PR #5977 merely broke the Bitwarden-side heuristics that are used to resolve the AssistStructure data for certain browsers, but I'm happy for that conjecture to be wrong and to learn something.

GiteaMirror commented

2026-04-11 01:41:19 -05:00

@androidacy-user commented on GitHub (Nov 18, 2025):

This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers.

There is also a separate issue with the latest version of Samsung Internet Browser (v29.x.x.x) that has broken compatibility with Autofill on older versions of the Android OS. This issue is something that needs to be handled by the browser developers.

Shouldn't you fallback automatically for unsupported browsers? Such an option is bound to scare off users from enabling it

@androidacy-user commented on GitHub (Nov 18, 2025): > This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers. > > There is also a separate issue with the latest version of Samsung Internet Browser (v29.x.x.x) that has broken compatibility with Autofill on older versions of the Android OS. This issue is something that needs to be handled by the browser developers. Shouldn't you fallback automatically for unsupported browsers? Such an option is bound to scare off users from enabling it

GiteaMirror commented

2026-04-11 01:41:19 -05:00

@gaiking-uk commented on GitHub (Nov 18, 2025):

Any ETA for the release date of the Android version (2025.11.0)?

2025.10.1 was released over a month ago at this point. The decision to not revert, and to leave the app broken for 10-20% of users this entire time is one thing, but given that is where we are, please can I ask that an interim update which includes the 'toggle option' is fast-tracked. This needs sorting now.

@gaiking-uk commented on GitHub (Nov 18, 2025): Any ETA for the release date of the Android version (2025.11.0)? 2025.10.1 was released over a month ago at this point. The decision to not revert, and to leave the app broken for 10-20% of users this entire time is one thing, but given that is where we are, please can I ask that an interim update which includes the 'toggle option' is fast-tracked. This needs sorting now.

GiteaMirror commented

2026-04-11 01:41:20 -05:00

@marcusbabajews commented on GitHub (Nov 18, 2025):

Galaxy S23 here. Been suffering with this for a while now. Extremely frustrating. Hoping there are eyes on this

@marcusbabajews commented on GitHub (Nov 18, 2025): Galaxy S23 here. Been suffering with this for a while now. Extremely frustrating. Hoping there are eyes on this

GiteaMirror commented

2026-04-11 01:41:20 -05:00

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

Surely this shouldn't be this hard to fix up

@Shadoxity commented on GitHub (Nov 19, 2025): Surely this shouldn't be this hard to fix up

GiteaMirror commented

2026-04-11 01:41:21 -05:00

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

I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill"

@fayelund commented on GitHub (Nov 19, 2025): I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill"

GiteaMirror commented

2026-04-11 01:41:21 -05:00

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

I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill"

What version are you on? Did you join the beta?

@free4ever commented on GitHub (Nov 19, 2025): > I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill" What version are you on? Did you join the beta?

GiteaMirror commented

2026-04-11 01:41:22 -05:00

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

I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill"

What version are you on? Did you join the beta?

Not a beta tester. Version 2025.11.0

@fayelund commented on GitHub (Nov 19, 2025): > > I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill" > > What version are you on? Did you join the beta? Not a beta tester. Version 2025.11.0

GiteaMirror commented

2026-04-11 01:41:22 -05:00

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

I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill"

What version are you on? Did you join the beta?

Not a beta tester. Version 2025.11.0

How did you get version 2025.11.0 when it's not released yet? Neither github or play store has that version. Even beta channel does not have that.

@sebtech33 commented on GitHub (Nov 19, 2025): > > > I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill" > > > > > > What version are you on? Did you join the beta? > > Not a beta tester. Version 2025.11.0 How did you get version 2025.11.0 when it's not released yet? Neither github or play store has that version. Even beta channel does not have that.

GiteaMirror commented

2026-04-11 01:41:23 -05:00

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

I have 2025.11.0 I just went to play store and clicked update

@Shadoxity commented on GitHub (Nov 19, 2025): I have 2025.11.0 I just went to play store and clicked update

GiteaMirror commented

2026-04-11 01:41:23 -05:00

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

I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill"

What version are you on? Did you join the beta?

Not a beta tester. Version 2025.11.0

How did you get version 2025.11.0 when it's not released yet? Neither github or play store has that version. Even beta channel does not have that.

It appeared in the play store as an update. Didn't do anything else than update

@fayelund commented on GitHub (Nov 19, 2025): > > > > I got the fixed version yesterday, just had to flip a switch in the autofill settings "Use compatibility mode for browser autofill" > > > > > > > > > What version are you on? Did you join the beta? > > > > Not a beta tester. Version 2025.11.0 > > How did you get version 2025.11.0 when it's not released yet? Neither github or play store has that version. Even beta channel does not have that. It appeared in the play store as an update. Didn't do anything else than update

GiteaMirror commented

2026-04-11 01:41:24 -05:00

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

Ok, I have not received that version yet. Play store says 2025.10.1 is the latest since 17. October. Look like I just need to wait. Weird to release on play store before github as it's usually the other way around, but ok 🤷‍♂️

@sebtech33 commented on GitHub (Nov 19, 2025): Ok, I have not received that version yet. Play store says 2025.10.1 is the latest since 17. October. Look like I just need to wait. Weird to release on play store before github as it's usually the other way around, but ok 🤷‍♂️

GiteaMirror commented

2026-04-11 01:41:24 -05:00

@david-livefront commented on GitHub (Nov 19, 2025):

The new app should be rolling out on the Play Store as we speak. The release should also be available publicly on GitHub now.

@david-livefront commented on GitHub (Nov 19, 2025): The new app should be rolling out on the Play Store as we speak. The release should also be available publicly on [GitHub](https://github.com/bitwarden/android/releases/tag/v2025.11.0-bwpm) now.

GiteaMirror commented

2026-04-11 01:41:25 -05:00

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

The new app should be rolling out on the Play Store as we speak. The release should also be available publicly on GitHub now.

Installed it, unfortunately don't see "use compatibility mode" toggle and without it it's still having the same issue as reported originally

@raywdude commented on GitHub (Nov 19, 2025): > The new app should be rolling out on the Play Store as we speak. The release should also be available publicly on [GitHub](https://github.com/bitwarden/android/releases/tag/v2025.11.0-bwpm) now. Installed it, unfortunately don't see "use compatibility mode" toggle and without it it's still having the same issue as reported originally

GiteaMirror commented

2026-04-11 01:41:25 -05:00

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

Hi all,

There was a small hiccup in our release process that resulted in the wrong build being tagged here in GitHub. The correct 2025.11.0 Release is now tagged, and aligns with the Play Store version that started rollout yesterday.

I double checked, and can confirm the option is indeed present on this build.

@SaintPatrck commented on GitHub (Nov 19, 2025): Hi all, There was a small hiccup in our release process that resulted in the wrong build being tagged here in GitHub. The correct [2025.11.0 Release](https://github.com/bitwarden/android/releases/tag/v2025.11.0-bwpm) is now tagged, and aligns with the Play Store version that started rollout yesterday. I double checked, and can confirm the option is indeed present on this build. <img width="365" src="https://github.com/user-attachments/assets/6aad435c-99d2-4064-b551-529c1d86ab09" />

GiteaMirror commented

2026-04-11 01:41:26 -05:00

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

Hi all,

There was a small hiccup in our release process that resulted in the wrong build being tagged here in GitHub. The correct 2025.11.0 Release is now tagged, and aligns with the Play Store version that started rollout yesterday.

I double checked, and can confirm the option is indeed present on this build.

This one worked, thanks!

@raywdude commented on GitHub (Nov 19, 2025): > Hi all, > > There was a small hiccup in our release process that resulted in the wrong build being tagged here in GitHub. The correct [2025.11.0 Release](https://github.com/bitwarden/android/releases/tag/v2025.11.0-bwpm) is now tagged, and aligns with the Play Store version that started rollout yesterday. > > I double checked, and can confirm the option is indeed present on this build. > > <img alt="" width="365" src="https://private-user-images.githubusercontent.com/1883101/516441662-6aad435c-99d2-4064-b551-529c1d86ab09.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjM1NzgxMzYsIm5iZiI6MTc2MzU3NzgzNiwicGF0aCI6Ii8xODgzMTAxLzUxNjQ0MTY2Mi02YWFkNDM1Yy05OWQyLTQwNjQtYjU1MS01MjljMWQ4NmFiMDkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MTExOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTExMTlUMTg0MzU2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZTg5ZWVjMTEzZWEwMDkyYzg2ZjRmNjBkOGRmOWEyMmFiMGZjNjM5M2E4YTExYWY4MmFjYTBjYWEwNzhhNGE4MSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.0_nCQpAY_rFQpN208-f8qIgCNc9BFQX4Dcusv6vlYZM"> This one worked, thanks!

GiteaMirror commented

2026-04-11 01:41:27 -05:00

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

No updates yet.

@SgtBatten commented on GitHub (Nov 19, 2025): No updates yet.

GiteaMirror commented

2026-04-11 01:41:27 -05:00

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

Thanks for pushing out a fix for this.

Is there a plan to push the new release to Bitwarden's FDroid repo? It looks like this normally happens in some sort of CI/CD workflow and is performed by a bot account. In this case the release process encountered some issues, so I wonder if the FDroid repo release process needs to be manually triggered.

@rallyemax commented on GitHub (Nov 19, 2025): Thanks for pushing out a fix for this. Is there a plan to push the new release to Bitwarden's FDroid repo? It looks like this normally happens in some sort of CI/CD workflow and is performed by a bot account. In this case the release process encountered some issues, so I wonder if the FDroid repo release process needs to be manually triggered.

GiteaMirror commented

2026-04-11 01:41:28 -05:00

@JLa2r commented on GitHub (Nov 20, 2025):

Yay! Works now with compatibility mode enabled. Thank you everyone involved.

@JLa2r commented on GitHub (Nov 20, 2025): Yay! Works now with compatibility mode enabled. Thank you everyone involved.

GiteaMirror commented

2026-04-11 01:41:29 -05:00

@SaintPatrck commented on GitHub (Nov 20, 2025):

Hi @rallyemax

The F-Droid repo is updated now. That process runs every evening and picks up non-draft releases. It's unrelated to the process that tags and creates our GitHub Releases, so it's unaffected by that issue. Since we fixed the GitHub release before the F-Droid process ran last night, the F-Droid release is the correct build. If you observe otherwise, or encounter any issues with it, let us know.

@SaintPatrck commented on GitHub (Nov 20, 2025): Hi @rallyemax The F-Droid repo is updated now. That process runs every evening and picks up non-draft releases. It's unrelated to the process that tags and creates our GitHub Releases, so it's unaffected by that issue. Since we fixed the GitHub release before the F-Droid process ran last night, the F-Droid release is the correct build. If you observe otherwise, or encounter any issues with it, let us know.

GiteaMirror commented

2026-04-11 01:41:29 -05:00

@rallyemax commented on GitHub (Nov 20, 2025):

Hi @rallyemax

The F-Droid repo is updated now. That process runs every evening and picks up non-draft releases. It's unrelated to the process that tags and creates our GitHub Releases, so it's unaffected by that issue. Since we fixed the GitHub release before the F-Droid process ran last night, the F-Droid release is the correct build. If you observe otherwise, or encounter any issues with it, let us know.

Hi @SaintPatrck,

It looks like the new version appears at the Bitwarden F-Droid repo Github page, but it didn't make it into the actual repo. This can be seen by browsing to https://mobileapp.bitwarden.com (which shows the most recent available version) or by examining the index-v1.json file inside the JAR archive at https://mobileapp.bitwarden.com/fdroid/repo/index-v1.jar -- the most recent version in that repo is 2025.10.1.

I'll be able to close this issue once the fixed version hits F-Droid and I can verify that the reported issue is resolved.

@rallyemax commented on GitHub (Nov 20, 2025): > Hi [@rallyemax](https://github.com/rallyemax) > > The F-Droid repo is updated now. That process runs every evening and picks up non-draft releases. It's unrelated to the process that tags and creates our GitHub Releases, so it's unaffected by that issue. Since we fixed the GitHub release before the F-Droid process ran last night, the F-Droid release is the correct build. If you observe otherwise, or encounter any issues with it, let us know. Hi @SaintPatrck, It looks like the new version appears at the [Bitwarden F-Droid repo Github page](https://github.com/bitwarden/f-droid), but it didn't make it into the actual repo. This can be seen by browsing to https://mobileapp.bitwarden.com (which shows the most recent available version) or by examining the index-v1.json file inside the JAR archive at https://mobileapp.bitwarden.com/fdroid/repo/index-v1.jar -- the most recent version in that repo is 2025.10.1. I'll be able to close this issue once the fixed version hits F-Droid and I can verify that the reported issue is resolved.

GiteaMirror commented

2026-04-11 01:41:30 -05:00

@SaintPatrck commented on GitHub (Nov 20, 2025):

@rallyemax Try now.

Thanks @vvolkgang! You're my hero. 🦸‍♂️

@SaintPatrck commented on GitHub (Nov 20, 2025): @rallyemax Try now. Thanks @vvolkgang! You're my hero. 🦸‍♂️

GiteaMirror commented

2026-04-11 01:41:30 -05:00

@rallyemax commented on GitHub (Nov 20, 2025):

@rallyemax Try now.

Thanks @vvolkgang! You're my hero. 🦸‍♂️

Got version 2025.11.0 in the F-Droid repo, installed it, and verified that when "Use compatibility mode for autofill" is disabled, the reported issue persists; but when that toggle is enabled, the reported issue is resolved.

Thank you Bitwarden devs for fixing the issue and @SaintPatrck for getting the new version pushed to the package repo.

@rallyemax commented on GitHub (Nov 20, 2025): > [@rallyemax](https://github.com/rallyemax) Try now. > > Thanks [@vvolkgang](https://github.com/vvolkgang)! You're my hero. 🦸‍♂️ Got version 2025.11.0 in the F-Droid repo, installed it, and verified that when "Use compatibility mode for autofill" is *disabled*, the reported issue persists; but when that toggle is *enabled*, the reported issue is resolved. Thank you Bitwarden devs for fixing the issue and @SaintPatrck for getting the new version pushed to the package repo.

GiteaMirror commented

2026-04-11 01:41:31 -05:00

@androidacy-user commented on GitHub (Nov 20, 2025):

Is the play store rollout limited or what? even in beta, PS is showing 2025.10.1 as the latest

@androidacy-user commented on GitHub (Nov 20, 2025): Is the play store rollout limited or what? even in beta, PS is showing 2025.10.1 as the latest

GiteaMirror commented

2026-04-11 01:41:32 -05:00

@gaiking-uk commented on GitHub (Nov 20, 2025):

It may depend on your region(?) The UK Play Store has 2025.11.0 available.

Also, just to confirm the setting that needs to be activated (as there are now 2x accessibility-related settings next to each other) is this one shown below.

Note: You do not need to enable BitWarden in the accessibility apps section for this option.

@gaiking-uk commented on GitHub (Nov 20, 2025): It may depend on your region(?) The UK Play Store has 2025.11.0 available. Also, just to confirm the setting that needs to be activated (as there are now 2x accessibility-related settings next to each other) is this one shown below. ![Image](https://github.com/user-attachments/assets/e2605d51-2106-41c9-a162-6028bf577067) Note: You do not need to enable BitWarden in the accessibility apps section for this option.

GiteaMirror commented

2026-04-11 01:41:33 -05:00

@SgtBatten commented on GitHub (Nov 21, 2025):

Yep still nothing in Australia either.

@SgtBatten commented on GitHub (Nov 21, 2025): Yep still nothing in Australia either.

GiteaMirror commented

2026-04-11 01:41:34 -05:00

@DaniRFernandes commented on GitHub (Nov 21, 2025):

Same thing in France for the Play Store version, it still shows 2025.10.1.

@DaniRFernandes commented on GitHub (Nov 21, 2025): Same thing in France for the Play Store version, it still shows 2025.10.1.

GiteaMirror commented

2026-04-11 01:41:35 -05:00

@shadow-helix commented on GitHub (Nov 21, 2025):

Still nothing in the UK Play Store for me. Has it only been released to the beta channel?

@shadow-helix commented on GitHub (Nov 21, 2025): Still nothing in the UK Play Store for me. Has it only been released to the beta channel?

GiteaMirror commented

2026-04-11 01:41:36 -05:00

@rainerzufall commented on GitHub (Nov 21, 2025):

I am on the beta channel and still haven't received the update :/

Edit: It landed in the beta channel 🥳

@rainerzufall commented on GitHub (Nov 21, 2025): I am on the beta channel and still haven't received the update :/ Edit: It landed in the beta channel 🥳

GiteaMirror commented

2026-04-11 01:41:37 -05:00

@androidacy-user commented on GitHub (Nov 22, 2025):

The new version has new issues with autofill in edge lmao. It keeps trying to fill the email in the password field, and insists there are no password fields for quick tile. Edge beta, was not an issue before 2025.10.1

@androidacy-user commented on GitHub (Nov 22, 2025): The new version has new issues with autofill in edge lmao. It keeps trying to fill the email in the password field, and insists there are no password fields for quick tile. Edge beta, was not an issue before 2025.10.1

GiteaMirror commented

2026-04-11 01:41:37 -05:00

@aryasenna commented on GitHub (Nov 22, 2025):

This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers.

I would argue the main issue is not technical compatibility, the issue is the lack of QA/Testing and/or total disregard of backward compatibility, breaking change, and lack of communication for non trivial number of user. Edge, Samsung Browser, and Opera users are likely not in the 0.1%.

Other users has pointed it several times, like this one:

The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill (#5977) that caused unexpected challenges with those specific browsers.

That PR affects 23 files, more than 260 lines of code changed, and the review was approved 6 minutes after being marked Ready for Review. This does not indicate a serious level of oversight. It has now caused a bug that is making the app unusable in browsers for a large proportion of your userbase.

Given the state of autofill in Android I would hope that changes that tighten it up even further would receive more oversight in the future.

6 minutes review, LGTM and there it goes to main?

The handling is even worse. Weeks before bug being tracked, another several weeks before it got fixed. Zero acknowledgement of the lack of oversight.

You already told us a bazillion times in PR language about "security improvement" and "challenge in compatibility". We know what they are and know they are normal part of software development, but users repeatedly asking explanation about your "challenge" in QA process got literally ignored and side-stepped.

Sincerely, a paying private customer and an enterprise user.

@aryasenna commented on GitHub (Nov 22, 2025): > This issue was caused by a change to Autofill with the purpose of improving security. Unfortunately, these affected browsers are not compatible with these improved security measures. The next release of the Android app will include a new toggle in the Autofill settings that change functionality in such a way that allows these browsers to Autofill properly again without negatively affecting the other browsers. I would argue the main issue is not technical compatibility, the issue is the lack of QA/Testing and/or total disregard of backward compatibility, breaking change, and lack of communication for non trivial number of user. Edge, Samsung Browser, and Opera users are likely not in the 0.1%. Other users has pointed it several times, like this one: > > The issues with mobile Edge, Opera and Samsung Internet are a result of tightening some security around autofill ([#5977](https://github.com/bitwarden/android/pull/5977)) that caused unexpected challenges with those specific browsers. > > That PR affects 23 files, more than 260 lines of code changed, and the review was approved 6 minutes after being marked Ready for Review. This does not indicate a serious level of oversight. It has now caused a bug that is making the app unusable in browsers for a large proportion of your userbase. > > Given the state of autofill in Android I would hope that changes that tighten it up even further would receive more oversight in the future. 6 minutes review, LGTM and there it goes to main? The handling is even worse. Weeks before bug being tracked, another several weeks before it got fixed. Zero acknowledgement of the lack of oversight. You already told us a bazillion times in PR language about "security improvement" and "challenge in compatibility". We know what they are and know they are normal part of software development, but users repeatedly asking explanation about your "challenge" in QA process got literally ignored and side-stepped. Sincerely, a paying private customer and an enterprise user.

GiteaMirror commented

2026-04-11 01:41:38 -05:00

@zzahkaboom24 commented on GitHub (Nov 22, 2025):

2025.11.0 with compatibility mode enabled works on Edge perfectly fine for me, thanks.

@zzahkaboom24 commented on GitHub (Nov 22, 2025): 2025.11.0 with compatibility mode enabled works on Edge perfectly fine for me, thanks.

GiteaMirror commented

2026-04-11 01:41:39 -05:00

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

Brave nightly, 2025.11.0 from France google playstore still not working with the new autofill option switched on.
Last update available seems to be 12 november 2025 on the App page log.

@Kazenn commented on GitHub (Nov 25, 2025): Brave nightly, 2025.11.0 from France google playstore still not working with the new autofill option switched on. Last update available seems to be 12 november 2025 on the App page log.

GiteaMirror commented

2026-04-11 01:41:40 -05:00

@androidacy-user commented on GitHub (Nov 29, 2025):

Ik glad that the Bitwarden team has released a solution, but we really shouldn't be forced to use compatibility mode on Chromium browsers for such a simple issue.

It's also unreliable now. Even GitHub.com it wants to fill the email in the password field in Edge

@androidacy-user commented on GitHub (Nov 29, 2025): > Ik glad that the Bitwarden team has released a solution, but we really shouldn't be forced to use compatibility mode on Chromium browsers for such a simple issue. It's also unreliable now. Even GitHub.com it wants to fill the email in the password field in Edge

GiteaMirror commented

2026-04-11 01:41:40 -05:00

@Cleroth commented on GitHub (Dec 3, 2025):

So since there's no response to this and they don't really seem to care, what is a good alternative?

@Cleroth commented on GitHub (Dec 3, 2025): So since there's no response to this and they don't really seem to care, what _is_ a good alternative?

GiteaMirror commented

2026-04-11 01:41:41 -05:00

@zzahkaboom24 commented on GitHub (Dec 3, 2025):

So since there's no response to this and they don't really seem to care, what is a good alternative?

They did respond, with a compatibility toggle in the latest version of the app.
That toggle should fix it for browsers lacking the new changes.

@zzahkaboom24 commented on GitHub (Dec 3, 2025): > So since there's no response to this and they don't really seem to care, what _is_ a good alternative? They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes.

GiteaMirror commented

2026-04-11 01:41:42 -05:00

@Cleroth commented on GitHub (Dec 3, 2025):

So since there's no response to this and they don't really seem to care, what is a good alternative?

They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes.

That toggle leaves you vulnerable to having your credentials stolen. Not exactly a "fix", just a poor workaround. If I wanted to be careless I wouldn't be using a password manager.

@Cleroth commented on GitHub (Dec 3, 2025): > > So since there's no response to this and they don't really seem to care, what _is_ a good alternative? > > They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes. That toggle leaves you vulnerable to having your credentials stolen. Not exactly a "fix", just a poor workaround. If I wanted to be careless I wouldn't be using a password manager.

GiteaMirror commented

2026-04-11 01:41:43 -05:00

@zzahkaboom24 commented on GitHub (Dec 3, 2025):

So since there's no response to this and they don't really seem to care, what is a good alternative?

They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes.

That toggle leaves you vulnerable to having your credentials stolen. Not exactly a "fix", just a poor workaround. If I wanted to be careless I wouldn't be using a password manager.

Then switch your browser.

The latest version of Chrome as far as I know does support autofill on pages correctly without compatibility mode.

@zzahkaboom24 commented on GitHub (Dec 3, 2025): > > > So since there's no response to this and they don't really seem to care, what _is_ a good alternative? > > > > They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes. > > That toggle leaves you vulnerable to having your credentials stolen. Not exactly a "fix", just a poor workaround. If I wanted to be careless I wouldn't be using a password manager. Then switch your browser. The latest version of Chrome as far as I know does support autofill on pages correctly without compatibility mode.

GiteaMirror commented

2026-04-11 01:41:43 -05:00

@Jebble commented on GitHub (Dec 3, 2025):

So since there's no response to this and they don't really seem to care, what is a good alternative?

They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes.

That toggle leaves you vulnerable to having your credentials stolen. Not exactly a "fix", just a poor workaround. If I wanted to be careless I wouldn't be using a password manager.

You're looking at it the wrong way around. Chrome and Brave implemented new more secure autofill solutions which Bitwarden supported. This broke the suggestions in other browsers that did not implement support for this yet. Bitwarden then added the compatibility mode to support these browser properly again.

Your credentials aren't any less secure then they were on Chrome or any other browser before. Your credentials are however more secure now on Chrome and Brave.

@Jebble commented on GitHub (Dec 3, 2025): > > > So since there's no response to this and they don't really seem to care, what _is_ a good alternative? > > > > > > They did respond, with a compatibility toggle in the latest version of the app. That toggle should fix it for browsers lacking the new changes. > > That toggle leaves you vulnerable to having your credentials stolen. Not exactly a "fix", just a poor workaround. If I wanted to be careless I wouldn't be using a password manager. You're looking at it the wrong way around. Chrome and Brave implemented new more secure autofill solutions which Bitwarden supported. This broke the suggestions in other browsers that did not implement support for this yet. Bitwarden then added the compatibility mode to support these browser properly again. Your credentials aren't any less secure then they were on Chrome or any other browser before. Your credentials are however more secure now on Chrome and Brave.

GiteaMirror commented

2026-04-11 01:41:44 -05:00

@Cleroth commented on GitHub (Dec 3, 2025):

I seem to remember this compatibility thing being around before this happened, but maybe I'm misremembering. If it is as you say, then I guess the only thing we can do is wait for Edge to update with the safer auto-fill...

@Cleroth commented on GitHub (Dec 3, 2025): I seem to remember this compatibility thing being around before this happened, but maybe I'm misremembering. If it is as you say, then I guess the only thing we can do is wait for Edge to update with the safer auto-fill...

GiteaMirror commented

2026-04-11 01:41:45 -05:00

@Jebble commented on GitHub (Dec 3, 2025):

I seem to remember this compatibility thing being around before this happened, but maybe I'm misremembering. If it is as you say, then I guess the only thing we can do is wait for Edge to update with the safer auto-fill...

I think whenever something like this happens they add a compatibility mode toggle to release a solution and (as they're doing now as well) then refactor that logic to be more included in the generic logic. This toggle will be removed in the next version and the functionality will automatically be on in browsers where it's required.

@Jebble commented on GitHub (Dec 3, 2025): > I seem to remember this compatibility thing being around before this happened, but maybe I'm misremembering. If it is as you say, then I guess the only thing we can do is wait for Edge to update with the safer auto-fill... I think whenever something like this happens they add a compatibility mode toggle to release a solution and (as they're doing now as well) then refactor that logic to be more included in the generic logic. This toggle will be removed in the next version and the functionality will automatically be on in browsers where it's required.

GiteaMirror commented

2026-04-11 01:41:46 -05:00

@DereckRadford commented on GitHub (Dec 4, 2025):

So what's the status on this. It's been occuring for over a month making the mobile app completely useless.

@DereckRadford commented on GitHub (Dec 4, 2025): So what's the status on this. It's been occuring for over a month making the mobile app completely useless.

GiteaMirror commented

2026-04-11 01:41:46 -05:00

@byteme4188 commented on GitHub (Dec 4, 2025):

The response on reddit has basically been its not their issue or problem

https://www.reddit.com/r/Bitwarden/s/DzP3dPCN1i

@byteme4188 commented on GitHub (Dec 4, 2025): The response on reddit has basically been its not their issue or problem https://www.reddit.com/r/Bitwarden/s/DzP3dPCN1i

GiteaMirror commented

2026-04-11 01:41:47 -05:00

@philipstratford commented on GitHub (Dec 4, 2025):

So what's the status on this. It's been occuring for over a month making the mobile app completely useless.

The mobile app isn't completely - or even slightly - useless. If you're using a browser which has implemented the more secure autofull mechanism then the app will work just fine with no further action. If you aren't, then until those browsers' manufacturers update their products you need to enable the compatibility mode toggle for autofill in the Bitwarden app's settings.

As has been said, this isn't Bitwarden's problem now. They released an update to support a more secure autofill mechanism, which I think we'd all like. But because some browsers don't yet support that mechanism Bitwarden (albeit belatedly) added a compatibility mode setting. I don't know what more people would like Bitwarden to do at this point.

@philipstratford commented on GitHub (Dec 4, 2025): > So what's the status on this. It's been occuring for over a month making the mobile app completely useless. The mobile app isn't completely - or even slightly - useless. If you're using a browser which has implemented the more secure autofull mechanism then the app will work just fine with no further action. If you aren't, then until those browsers' manufacturers update their products you need to enable the compatibility mode toggle for autofill in the Bitwarden app's settings. As has been said, this _isn't_ Bitwarden's problem now. They released an update to support a more secure autofill mechanism, which I think we'd all like. But because some browsers don't yet support that mechanism Bitwarden (albeit belatedly) added a compatibility mode setting. I don't know what more people would like Bitwarden to do at this point.

GiteaMirror commented

2026-04-11 01:41:48 -05:00

@johnfromstatefarm commented on GitHub (Dec 4, 2025):

Why did this get closed? I don't see any new update fixing this? It's been a month guys, come on!

@johnfromstatefarm commented on GitHub (Dec 4, 2025): Why did this get closed? I don't see any new update fixing this? It's been a month guys, come on!

GiteaMirror commented

2026-04-11 01:41:49 -05:00

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

Hi @johnfromstatefarm

This issue was closed as completed by the author, here.

As others have noted, 2025.11.0 contains a compatibility toggle which resolves the issue. An upcoming release removes the toggle and enables compatibility mode for affected browsers by default.

If you are still experiencing issues please open a new ticket with details specific to your case.

@SaintPatrck commented on GitHub (Dec 4, 2025): Hi @johnfromstatefarm This issue was closed as completed by the author, [here](https://github.com/bitwarden/android/issues/6107#issuecomment-3559844659). As others have noted, 2025.11.0 contains a compatibility toggle which resolves the issue. An upcoming release removes the toggle and enables compatibility mode for affected browsers by default. If you are still experiencing issues please open a new ticket with details specific to your case.

GiteaMirror commented

2026-04-11 01:41:50 -05:00

@androidacy-user commented on GitHub (Dec 4, 2025):

So what's the status on this. It's been occuring for over a month making the mobile app completely useless.

The mobile app isn't completely - or even slightly - useless. If you're using a browser which has implemented the more secure autofull mechanism then the app will work just fine with no further action. If you aren't, then until those browsers' manufacturers update their products you need to enable the compatibility mode toggle for autofill in the Bitwarden app's settings.

As has been said, this isn't Bitwarden's problem now. They released an update to support a more secure autofill mechanism, which I think we'd all like. But because some browsers don't yet support that mechanism Bitwarden (albeit belatedly) added a compatibility mode setting. I don't know what more people would like Bitwarden to do at this point.

Thing is - it is bitwardens problem. Even with that compatibility mode on, weird issues persist that weren't present before the change.

And if people are using chrome, I suspect they probably also use Google password manager, NOT bitwarden.

Bitwarden broke existing functionality. Using the newer, more secure autofill is totally valid, breaking existing users/browsers isn't.

As I stated above, edge very intentionally doesn't implement the newer autofill, and I suspect they have a good reason for it.

Bitwarden sells a paid product, but shrugs this off as "your fault"? I don't think it's unreasonable for people to be upset at this response, and especially at the 1-2 months it took to ship a fix for the feature that broke the core functionality which the PR for was approved in minutes.

At minimum this suggests lackluster testing. At worst, it suggests bitwarden only intends to support chrome going forward.

@androidacy-user commented on GitHub (Dec 4, 2025): > > So what's the status on this. It's been occuring for over a month making the mobile app completely useless. > > The mobile app isn't completely - or even slightly - useless. If you're using a browser which has implemented the more secure autofull mechanism then the app will work just fine with no further action. If you aren't, then until those browsers' manufacturers update their products you need to enable the compatibility mode toggle for autofill in the Bitwarden app's settings. > > As has been said, this _isn't_ Bitwarden's problem now. They released an update to support a more secure autofill mechanism, which I think we'd all like. But because some browsers don't yet support that mechanism Bitwarden (albeit belatedly) added a compatibility mode setting. I don't know what more people would like Bitwarden to do at this point. Thing is - it is bitwardens problem. Even with that compatibility mode on, weird issues persist that weren't present before the change. And if people are using chrome, I suspect they probably also use Google password manager, NOT bitwarden. **Bitwarden** broke existing functionality. Using the newer, more secure autofill is totally valid, breaking existing users/browsers isn't. As I stated above, edge very intentionally doesn't implement the newer autofill, and I suspect they have a good reason for it. Bitwarden sells a paid product, but shrugs this off as "your fault"? I don't think it's unreasonable for people to be upset at this response, and especially at the 1-2 months it took to ship a fix for the feature that broke the core functionality which the PR for was approved in minutes. At minimum this suggests lackluster testing. At worst, it suggests bitwarden only intends to support chrome going forward.

GiteaMirror commented

2026-04-11 01:41:51 -05:00

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

@androidacy-user:

Even with that compatibility mode on, weird issues persist that weren't present before the change.

I think @SaintPatrck just a few hours before your post suggested "If you are still experiencing issues please open a new ticket with details specific to your case."

And if people are using chrome, I suspect they probably also use Google password manager, NOT bitwarden.
...
At worst, it suggests bitwarden only intends to support chrome going forward.

Chrome and Brave can be used with the new "autofill integrations". - And as it seems, that "choice" is only based on which browsers do or don't support the new, more modern and secure autofill functions.

@pamperer562580892423 commented on GitHub (Dec 4, 2025): @androidacy-user: > Even with that compatibility mode on, weird issues persist that weren't present before the change. I think @SaintPatrck just a few hours before your post suggested "If you are still experiencing issues please open a new ticket with details specific to your case." > And if people are using chrome, I suspect they probably also use Google password manager, NOT bitwarden. > ... > At worst, it suggests bitwarden only intends to support chrome going forward. Chrome **and Brave** can be used with the new ["autofill integrations"](https://bitwarden.com/help/auto-fill-android/#browser-integrations). - And as it seems, that "choice" is only based on which browsers do or don't support the new, more modern and secure autofill functions.

GiteaMirror commented

2026-04-11 01:41:52 -05:00

@Cleroth commented on GitHub (Dec 4, 2025):

Right, I understand making a change you don't realize would have such repercussions, but it shouldn't take over a month to have provided automatic "compatibility mode" for non-supporting browsers. Additional security should be optional, not forced or hidden behind a toggle most users don't know about. Then at best Bitwarden could've provided a warning about current browser being less secure than others.

I'm sure this is still affecting a whole lot of users. I myself have been experiencing it for a while but just shrugged it off figuring it would eventually get fixed, until getting so tired of it I looked it up. I suspect the majority of people don't bother or just leave a negative review on the app stores.

@Cleroth commented on GitHub (Dec 4, 2025): Right, I understand making a change you don't realize would have such repercussions, but it shouldn't take over a month to have provided automatic "compatibility mode" for non-supporting browsers. Additional security should be optional, not forced or hidden behind a toggle most users don't know about. Then at best Bitwarden could've provided a warning about current browser being less secure than others. I'm sure this is _still_ affecting a whole lot of users. I myself have been experiencing it for a while but just shrugged it off figuring it would eventually get fixed, until getting so tired of it I looked it up. I suspect the majority of people don't bother or just leave a negative review on the app stores.

GiteaMirror commented

2026-04-11 01:41:53 -05:00

@androidacy-user commented on GitHub (Dec 4, 2025):

@androidacy-user:

Even with that compatibility mode on, weird issues persist that weren't present before the change.

I think @SaintPatrck just a few hours before your post suggested "If you are still experiencing issues please open a new ticket with details specific to your case."

And if people are using chrome, I suspect they probably also use Google password manager, NOT bitwarden.
...
At worst, it suggests bitwarden only intends to support chrome going forward.

Chrome and Brave can be used with the new "autofill integrations". - And as it seems, that "choice" is only based on which browsers do or don't support the new, more modern and secure autofill functions.

Ahem, brave stable and chrome stable. Even non stable versions fall back to compatibility mode :)

It very much is related to the original issue, because they didn't actually fix the issue, instead preferring to barely workaround it, and tell users they're using the wrong browser.

Again, the response was downright awful, and the issue was not fully addressed.

@androidacy-user commented on GitHub (Dec 4, 2025): > @androidacy-user: > > > Even with that compatibility mode on, weird issues persist that weren't present before the change. > > I think @SaintPatrck just a few hours before your post suggested "If you are still experiencing issues please open a new ticket with details specific to your case." > > > And if people are using chrome, I suspect they probably also use Google password manager, NOT bitwarden. > > ... > > At worst, it suggests bitwarden only intends to support chrome going forward. > > Chrome **and Brave** can be used with the new ["autofill integrations"](https://bitwarden.com/help/auto-fill-android/#browser-integrations). - And as it seems, that "choice" is only based on which browsers do or don't support the new, more modern and secure autofill functions. Ahem, brave stable and chrome stable. Even non stable versions fall back to compatibility mode :) It very much is related to the original issue, because they didn't actually fix the issue, instead preferring to barely workaround it, and tell users they're using the wrong browser. Again, the response was downright awful, and the issue was not fully addressed.

GiteaMirror commented

2026-04-11 01:41:53 -05:00

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

Ahem, brave stable and chrome stable. Even non stable versions fall back to compatibility mode :)

As far as I understand this, this is wrong for two reasons:

At least Chrome Beta can also be toggled in the autofill integrations.

Only Edge, Opera and Samsung Internet were part of that "compatibility mode". E.g. in the previous Help Sites section for the compatibility mode, Firefox was mentioned as "secure" and not as part of the compatibility mode. (though I wished they would now also make it more clear which browser falls under which category)

It very much is related to the original issue, because they didn't actually fix the issue, instead preferring to barely workaround it, and tell users they're using the wrong browser.

What was the original issue in your opinion?? -- I think others already wrote it here: they made autofill more secure - didn't work on some browsers (because those browsers lack compatibility for those new options) - so they fall back to, as I understand it, more or less the way autofill worked before in those browsers.

They didn't make autofill less secure in those browser as before - they made autofill more secure in those browser where it was possible.

So, what's the original issue?

The original issue seems to really be: those browsers lack compatibility for those new options. Whether you like it or not.

@pamperer562580892423 commented on GitHub (Dec 4, 2025): > Ahem, brave stable and chrome stable. Even non stable versions fall back to compatibility mode :) As far as I understand this, this is wrong for two reasons: 1. At least Chrome Beta can also be toggled in the autofill integrations. <img width="400" height="281" alt="Image" src="https://github.com/user-attachments/assets/973e324a-4b4c-4dc9-afd4-fbc14aafa54e" /> 2. Only Edge, Opera and Samsung Internet were part of that "compatibility mode". E.g. in the previous Help Sites section for the compatibility mode, Firefox was mentioned as "secure" and not as part of the compatibility mode. (though I wished they would now also make it more clear which browser falls under which category) > It very much is related to the original issue, because they didn't actually fix the issue, instead preferring to barely workaround it, and tell users they're using the wrong browser. What was the original issue in your opinion?? -- I think others already wrote it here: they made autofill more secure - didn't work on some browsers (because those browsers _**lack compatibility**_ for those new options) - so they fall back to, as I understand it, more or less the way autofill worked before in those browsers. They didn't make autofill less secure in those browser as before - they made autofill more secure in those browser where it was possible. So, what's the original issue? The original issue seems to really be: those browsers _**lack compatibility**_ for those new options. Whether you like it or not.

GiteaMirror commented

2026-04-11 01:41:54 -05:00

@Cleroth commented on GitHub (Dec 4, 2025):

those browsers lack compatibility for those new options. Whether you like it or not.

"Your browser that has worked with this and is used by hundreds of millions is less secure than my browser so now it won't work. Sucks to be you."

@Cleroth commented on GitHub (Dec 4, 2025): > those browsers lack compatibility for those new options. Whether you like it or not. "Your browser that has worked with this and is used by hundreds of millions is less secure than my browser so now it won't work. Sucks to be you."

GiteaMirror commented

2026-04-11 01:41:55 -05:00

@Cieptak commented on GitHub (Dec 10, 2025):

The bug was fixed in the update to version 2025.11.1

@Cieptak commented on GitHub (Dec 10, 2025): The bug was fixed in the update to version 2025.11.1

Sign in to join this conversation.

Branches Tags

main

sdlc/sdk-update

new-item-types/PM-32810_bank-account-view

new-item-types/PM-32810_bank-account

beta-for-qa

BWA-253/not-displaying-totp-coded-with-empty-key

target-sdk-37

vvolkgang/renovate-remove-group

pm-34038/card-scanner-qa-fixes

PM-33982/build-device-screen

PM-30625/filter-out-empty-totp-vault-count

vvolkgang/update-jira-release-notes

new-item-types/PM-34123_new-item-menu

new-item-types/PM-32806_passport

new-item-types/PM-32808_drivers-license

BWA-99/show-next-totp

BWA-99/add-preview-next-totp-code-setting

renovate/glidecompose

chore/improve-android-ui-verification-skill

sync-min-sdk

release/2026.4-rc51

fix/security-sast-22741894-bvwj

related-origin-passkey-creation

release/2026.4-rc50

platform/android-breaking-change-detection

innovation-sprint-2026-send-folder

release/2026.3-rc49

PM-34193-vault-lockout

android-collections

llm/add-resolving-sdk-updates-skill

QA-1523/sanity-test-saucelabs

release/2026.3-rc48

PM-26577-app-links-support

PM-26896-autofill-fix

release/2026.2-rc47

pr-6572

release/2026.2-rc46

release/2026.1-rc45

PM-30644/added-logs-for-debug

PM-30644/quicktile-nav-not-showing-migration

minor-gradle-updates

release/2026.1-rc42

release/2026.1-rc44

release/2026.1-rc43

PM-28834/set-landscape-on-horizonos-devices

PM-28468/validate-and-navigate-to-vault-migration

PM-20026/force-ltr-passwords-and-codes

release/2025.12-rc41

cmcg/testCoverage

PM-29014/talkback-support-for-passwords

release/2025.12-rc40

BRE-1305/publish_test

accept-user-certs

autofill-permissions

release/2025.11-rc39

PM-22479/check-all-certificates-validate-asset-links

release/2025.10-rc38

agalles/android-latest

retro-agent

PM-27001/skip-account-selection-only-one-exists-cxp

release/2025.10-rc37

agalles/test-1118

release/2025.10-rc36

PM-20593-token-refresh

QA-1126b/adding-native-sanity-test

release/2025.9-rc35

pm-25933/sdk-update-password

release/2025.9-rc34

release/2025.8-rc33

agalles/20250821-release

debug-release-issues

pm-24249-allow-automated-prs-for-sdk-updates

release/2025.8-rc32

release/WORKFLOW-TEST-2025.8-rc28

agalles/20250807release

release/2025.07-rc25

release/hotfix-v2025.7.0-bwa

pm-23311/export-vault-policy-bypass

release/2025.07-rc24

authenticator-pm-sync-flags-issue

release/hotfix-v2025.6.0-bwpm

release/2025.06-rc21

agalles/automate-android-fastlane-patch

release/2025.05-rc20

release/2025.04-rc19

languages/basque

release/2025.03-rc19

update-readme

qrcode/feature

innovation/archive/pm-19153-archive-items

qrcode/2-ui-fields

qrcode/1-page

hold-on-biometric-prompt-alternative

release-notes-process

release/2025.02-rc16

bwa-monorepo

PM-8223/new-device-verification-ux-improvements

pm-18451/exempt-from-policies

test-bwa

release/2025.01-rc15

release/2025.01-rc14

release/2024.12-rc13

pm-16670/sync-leave-notice

821

PM-16695/backport-lean-more-new-device-verification

release/hotfix-v2024.11.7

release/2024.11-rc1

pm-11304/collection-add-item-button

PM-14241/disabling-logs-app-crash

poc/offline-editing

new-version-calc

pm-11649/expired-link-services

pm-6702/add-feature-flag

pm-6702/email-verification-feature

pm-9933/marketing-copy-update

pm-6702/registration-flows

update-templates

pm-6701/email-verification-selfhost-registration

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/android#8403