github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 00:09:31 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5278] Autofill has been totally broken since the UI overhaul #8268

New Issue
Open
opened 2026-04-11 01:24:59 -05:00 by GiteaMirror · 25 comments
GiteaMirror commented 2026-04-11 01:24:59 -05:00
Owner
Copy Link

Originally created by @Aashishkebab on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5278

Steps To Reproduce

  1. Open an app or website.
  2. Click the password on the keyboard.
  3. Nothing happens.
  4. Try using the Autofill quick settings.
  5. Nothing happens.
  6. Try again.
  7. Nothing happens.
  8. Click the quick settings tile again.
  9. It will open BitWarden. Sometimes.

Expected Result

The app to actually work.

Actual Result

Autofill is broken. Sometimes. It isn't consistent.

Screenshots or Videos

Video won't upload. Google Photos link: https://photos.app.goo.gl/d8oaVtdx4n98RBXAA

Additional Context

This issue isn't consistent. Sometimes it will randomly work the first try. Sometimes the quick settings tile will work. Sometimes the quick settings tile will work on the second try after clicking out of and back into the input field. (in this particular video, it didn't no matter how many times I clicked it).

This issue is not specific to any browser or app. It is system-wide.

Build Version

2025.4.0 (20100)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Google Pixel 9 Pro

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @Aashishkebab on GitHub (May 28, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5278 ### Steps To Reproduce 1. Open an app or website. 2. Click the password on the keyboard. 3. Nothing happens. 4. Try using the Autofill quick settings. 5. Nothing happens. 6. Try again. 7. Nothing happens. 8. Click the quick settings tile again. 9. It will open BitWarden. Sometimes. ### Expected Result The app to actually work. ### Actual Result Autofill is broken. Sometimes. It isn't consistent. ### Screenshots or Videos Video won't upload. Google Photos link: https://photos.app.goo.gl/d8oaVtdx4n98RBXAA ### Additional Context This issue isn't consistent. Sometimes it will randomly work the first try. Sometimes the quick settings tile will work. Sometimes the quick settings tile will work on the second try after clicking out of and back into the input field. (in this particular video, it didn't no matter how many times I clicked it). This issue is not specific to any browser or app. It is system-wide. ### Build Version 2025.4.0 (20100) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Google Pixel 9 Pro ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:password-managerbug labels 2026-04-11 01:24:59 -05:00
GiteaMirror commented 2026-04-11 01:25:02 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (May 28, 2025):

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

<!-- gh-comment-id:2916993745 --> @bitwarden-bot commented on GitHub (May 28, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22167
GiteaMirror commented 2026-04-11 01:25:03 -05:00
Author
Owner
Copy Link

@jtodddd commented on GitHub (May 29, 2025):

Hi there,

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

Thanks!

<!-- gh-comment-id:2919322921 --> @jtodddd commented on GitHub (May 29, 2025): Hi there, Thanks for this report, it 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:25:05 -05:00
Author
Owner
Copy Link

@fotex commented on GitHub (May 31, 2025):

Hi,

I had the same problem and I fixed it by cleaning up Google keyboard cache.

<!-- gh-comment-id:2924431072 --> @fotex commented on GitHub (May 31, 2025): Hi, I had the same problem and I fixed it by cleaning up Google keyboard cache.
GiteaMirror commented 2026-04-11 01:25:05 -05:00
Author
Owner
Copy Link

@Aashishkebab commented on GitHub (May 31, 2025):

Hi,

I had the same problem and I fixed it by cleaning up Google keyboard cache.

That doesn't do anything for me.

<!-- gh-comment-id:2925162660 --> @Aashishkebab commented on GitHub (May 31, 2025): > Hi, > > I had the same problem and I fixed it by cleaning up Google keyboard cache. That doesn't do anything for me.
GiteaMirror commented 2026-04-11 01:25:06 -05:00
Author
Owner
Copy Link

@tassoevan commented on GitHub (Jun 4, 2025):

Apparently wiping the whole Gboard data worked. Not sure why. As the configuration was reset, I wonder which specific setting might be blocking the auto fill service.

<!-- gh-comment-id:2939241091 --> @tassoevan commented on GitHub (Jun 4, 2025): Apparently wiping the whole Gboard data worked. Not sure why. As the configuration was reset, I wonder which specific setting might be blocking the auto fill service.
GiteaMirror commented 2026-04-11 01:25:07 -05:00
Author
Owner
Copy Link

@miberecz commented on GitHub (Jun 4, 2025):

I can confirm that something is wrong with Gboard. If I delete/disable it, the built in keyboard (Samsung in my case) offers the Bitwarden autofill. Gboard do not, no matter what I do

<!-- gh-comment-id:2940137276 --> @miberecz commented on GitHub (Jun 4, 2025): I can confirm that something is wrong with Gboard. If I delete/disable it, the built in keyboard (Samsung in my case) offers the Bitwarden autofill. Gboard do not, no matter what I do
GiteaMirror commented 2026-04-11 01:25:08 -05:00
Author
Owner
Copy Link

@thinkingofmaud commented on GitHub (Jun 9, 2025):

i'm having issues with autofill

I usually use patterns with 'start with' and i close it with a slash, as in https:/domain.name/ so i can prevent against attacks like https://domain.name.scam, because there is no option for 'exact domain name' on bitwarden.

it works fine with desktop, not fine on iceraven.

<!-- gh-comment-id:2954617236 --> @thinkingofmaud commented on GitHub (Jun 9, 2025): i'm having issues with autofill I usually use patterns with 'start with' and i close it with a slash, as in https:/domain.name/ so i can prevent against attacks like https://domain.name.scam, because there is no option for 'exact domain name' on bitwarden. it works fine with desktop, not fine on iceraven.
GiteaMirror commented 2026-04-11 01:25:09 -05:00
Author
Owner
Copy Link

@cnoderer commented on GitHub (Jun 14, 2025):

@tassoevan Thank you for this comment, i'm having the same problem with gboard. First tried only deleting cache, didn't help.
After deleting App-data it worked again.

<!-- gh-comment-id:2972657572 --> @cnoderer commented on GitHub (Jun 14, 2025): @tassoevan Thank you for this comment, i'm having the same problem with gboard. First tried only deleting cache, didn't help. After deleting App-data it worked again.
GiteaMirror commented 2026-04-11 01:25:10 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Jun 16, 2025):

The combination of Disabling inline autofill in Bitwarden and Suggestions in GBoard appear to work reliably for users, as mentioned in this comment.

<!-- gh-comment-id:2977584323 --> @SaintPatrck commented on GitHub (Jun 16, 2025): The combination of Disabling inline autofill in Bitwarden and Suggestions in GBoard appear to work reliably for users, as mentioned in [this comment](https://github.com/bitwarden/android/issues/5341#issuecomment-2959578647).
GiteaMirror commented 2026-04-11 01:25:10 -05:00
Author
Owner
Copy Link

@Ri-Dearg commented on GitHub (Jun 24, 2025):

The combination of Disabling inline autofill in Bitwarden and Suggestions in GBoard appear to work reliably for users, as mentioned in this comment.

I've seen that issue but it's closed, however, I still think this is an issue. I posted this comment there, but if you think there's a better place to post this, please let me know.

I previously I had these two options available to use at the same time. They weren't exclusive for me. I could have both the on-screen popup and the Inline showing. I don't remember how long ago it was, but it was that way for a few years until maybe this year.

There is no reason that this behaviour should have been changed.

  • These are two, separate options in the menu which can both be toggled on.
  • There is no help text indicating they are exclusive.
  • there is no visual signal they are exclusive e.g. Toggling one option on greys out the other.
  • They are often useful for different scenarios. For example, I have loads of logins to certain sites and inline is unclear, the popup is much easier to read.
  • The inline is faster for simple logins.
  • the popup box often detects fields that inline does not. But if I have inline turned on, the box never shows even if a field would be detected by popup. That means I manually have to use the settings shortcut to copy and paste which is tedious. I never had to do this before.
  • the user should be able to decide what combo suits them anyway, without hidden bitwarden preferences.

This should be returned to its previous behaviour of both options being available, as the settings menu itself suggests.

<!-- gh-comment-id:3001702120 --> @Ri-Dearg commented on GitHub (Jun 24, 2025): > The combination of Disabling inline autofill in Bitwarden and Suggestions in GBoard appear to work reliably for users, as mentioned in [this comment](https://github.com/bitwarden/android/issues/5341#issuecomment-2959578647). I've seen that issue but it's closed, however, I still think this is an issue. I posted this comment there, but if you think there's a better place to post this, please let me know. I previously I had these two options available to use at the same time. They weren't exclusive for me. I could have both the on-screen popup and the Inline showing. I don't remember how long ago it was, but it was that way for a few years until maybe this year. There is no reason that this behaviour should have been changed. - These are two, separate options in the menu which can both be toggled on. - There is no help text indicating they are exclusive. - there is no visual signal they are exclusive e.g. Toggling one option on greys out the other. - They are often useful for different scenarios. For example, I have loads of logins to certain sites and inline is unclear, the popup is much easier to read. - The inline is faster for simple logins. - the popup box often detects fields that inline does not. But if I have inline turned on, the box never shows even if a field would be detected by popup. That means I manually have to use the settings shortcut to copy and paste which is tedious. I never had to do this before. - the user should be able to decide what combo suits them anyway, without hidden bitwarden preferences. This should be returned to its previous behaviour of both options being available, as the settings menu itself suggests.
GiteaMirror commented 2026-04-11 01:25:11 -05:00
Author
Owner
Copy Link

@Aashishkebab commented on GitHub (Jun 24, 2025):

That does not "reliably work for users". It does not. Yet people keep saying it does.

<!-- gh-comment-id:3001708901 --> @Aashishkebab commented on GitHub (Jun 24, 2025): That does not "reliably work for users". It does not. Yet people keep saying it does.
GiteaMirror commented 2026-04-11 01:25:12 -05:00
Author
Owner
Copy Link

@LaCocoRoco commented on GitHub (Jun 27, 2025):

Hi,

I had the same problem and I fixed it by cleaning up Google keyboard cache.

You are my hero! Thank you! Clearing cache and data from Gboard fixed the problem.

<!-- gh-comment-id:3013893252 --> @LaCocoRoco commented on GitHub (Jun 27, 2025): > Hi, > > I had the same problem and I fixed it by cleaning up Google keyboard cache. You are my hero! Thank you! Clearing cache and data from Gboard fixed the problem.
GiteaMirror commented 2026-04-11 01:25:12 -05:00
Author
Owner
Copy Link

@LokIsLoki commented on GitHub (Jul 1, 2025):

Clearing cache and data in Gboard did not resolve this issue for me, nor did disabling inline autofill (BW) and suggestions (Gboard)

Android 12, S10, Brave

<!-- gh-comment-id:3021571554 --> @LokIsLoki commented on GitHub (Jul 1, 2025): Clearing cache and data in Gboard did not resolve this issue for me, nor did disabling inline autofill (BW) and suggestions (Gboard) Android 12, S10, Brave
GiteaMirror commented 2026-04-11 01:25:13 -05:00
Author
Owner
Copy Link

@LaCocoRoco commented on GitHub (Jul 1, 2025):

It looks like that after some time when selecting a input field the Inline popup will not appear anymore (After clearing GBoard cache and data). Surprisingly there is a setting "Show list of suggestions" in the GBoard "Spell check" settings which will give the possibility to select the autofill from the keyboard (My settings are in German and i do not know the direct translations). In addition i sometimes have to start the Bitwarden app first and then change back to the login page of the page i want to login or remove the content of an input field first.

<!-- gh-comment-id:3025286276 --> @LaCocoRoco commented on GitHub (Jul 1, 2025): It looks like that after some time when selecting a input field the Inline popup will not appear anymore (After clearing GBoard cache and data). Surprisingly there is a setting "Show list of suggestions" in the GBoard "Spell check" settings which will give the possibility to select the autofill from the keyboard (My settings are in German and i do not know the direct translations). In addition i sometimes have to start the Bitwarden app first and then change back to the login page of the page i want to login or remove the content of an input field first.
GiteaMirror commented 2026-04-11 01:25:14 -05:00
Author
Owner
Copy Link

@cavililla commented on GitHub (Jul 4, 2025):

In bitwarden.eu and Samsung Galaxy A52s 5G happend the same

<!-- gh-comment-id:3035059599 --> @cavililla commented on GitHub (Jul 4, 2025): In bitwarden.eu and Samsung Galaxy A52s 5G happend the same
GiteaMirror commented 2026-04-11 01:25:15 -05:00
Author
Owner
Copy Link

@IamSingh01 commented on GitHub (Jul 4, 2025):

Even the autofill from the notification toggle doesn't work. They 1st removed it completely but then on requests they reintroduced but it never worked.

<!-- gh-comment-id:3037171645 --> @IamSingh01 commented on GitHub (Jul 4, 2025): Even the autofill from the notification toggle doesn't work. They 1st removed it completely but then on requests they reintroduced but it never worked.
GiteaMirror commented 2026-04-11 01:25:15 -05:00
Author
Owner
Copy Link

@Aashishkebab commented on GitHub (Jul 16, 2025):

Why does nobody seem to care that this is completely and utterly broken? It is so frustrating.

<!-- gh-comment-id:3078387666 --> @Aashishkebab commented on GitHub (Jul 16, 2025): Why does nobody seem to care that this is completely and utterly broken? It is so frustrating.
GiteaMirror commented 2026-04-11 01:25:16 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Jul 18, 2025):

Some changes have been made to work in conjunction with the updates Google has made in Chrome to support native autofill.

We have also updated the UI for the Autofill Settings screen to better illustrate how the features work. Note: These UI changes are to help users better understand the different autofill settings, but no functional changes were made to these settings.

We hope these UI updates and changes to how we interact with native autofill result in a better autofill experience.

All of this will be in the upcoming release of the app later this month.

<!-- gh-comment-id:3090733366 --> @david-livefront commented on GitHub (Jul 18, 2025): Some changes have been made to work in conjunction with the updates Google has made in Chrome to support native autofill. We have also updated the UI for the Autofill Settings screen to better illustrate how the features work. Note: These UI changes are to help users better understand the different autofill settings, but no functional changes were made to these settings. We hope these UI updates and changes to how we interact with native autofill result in a better autofill experience. All of this will be in the upcoming release of the app later this month.
GiteaMirror commented 2026-04-11 01:25:17 -05:00
Author
Owner
Copy Link

@Aashishkebab commented on GitHub (Jul 18, 2025):

Some changes have been made to work in conjunction with the updates Google has made in Chrome to support native autofill.

We have also updated the UI for the Autofill Settings screen to better illustrate how the features work. Note: These UI changes are to help users better understand the different autofill settings, but no functional changes were made to these settings.

We hope these UI updates and changes to how we interact with native autofill result in a better autofill experience.

All of this will be in the upcoming release of the app later this month.

None of this changes the fact that it DOESN'T WORK.

<!-- gh-comment-id:3090737986 --> @Aashishkebab commented on GitHub (Jul 18, 2025): > Some changes have been made to work in conjunction with the updates Google has made in Chrome to support native autofill. > > We have also updated the UI for the Autofill Settings screen to better illustrate how the features work. Note: These UI changes are to help users better understand the different autofill settings, but no functional changes were made to these settings. > > We hope these UI updates and changes to how we interact with native autofill result in a better autofill experience. > > All of this will be in the upcoming release of the app later this month. None of this changes the fact that it DOESN'T WORK.
GiteaMirror commented 2026-04-11 01:25:17 -05:00
Author
Owner
Copy Link

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

Screenshot_20250918-095121.png

Evidence that multiple people are having this issue.

<!-- gh-comment-id:3307584171 --> @Aashishkebab commented on GitHub (Sep 18, 2025): ![Screenshot_20250918-095121.png](https://github.com/user-attachments/assets/882c2a11-7512-436e-a0c4-8987f4d3aa07) Evidence that multiple people are having this issue.
GiteaMirror commented 2026-04-11 01:25:19 -05:00
Author
Owner
Copy Link

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

Same here, I use self-hosted Bitwarden. I've got two devices where I experience the same problem: Pixel 9 Pro and Lenovo Legion Y700 2025 (ROW). I also use different keyboards: Gboard on the phone and FUTO on the tablet.

For now I'm able to use autofill like this:

  1. Encounter login page - keyboard asks to unlock Bitwarden
  2. Successfully unlock Bitwarden and select an entry for current website
  3. Username and password are not filled. Opening keyboard and selecting a password entry does nothing (if it appears at all)
  4. Close Chrome via Recents screen and open it again
  5. Now autofill entries show up in the keyboard and work

Rinse and repeat every time you have an issue.

<!-- gh-comment-id:3308006595 --> @endervad commented on GitHub (Sep 18, 2025): Same here, I use self-hosted Bitwarden. I've got two devices where I experience the same problem: Pixel 9 Pro and Lenovo Legion Y700 2025 (ROW). I also use different keyboards: Gboard on the phone and FUTO on the tablet. For now I'm able to use autofill like this: 1. Encounter login page - keyboard asks to unlock Bitwarden 2. Successfully unlock Bitwarden and select an entry for current website 3. Username and password are not filled. Opening keyboard and selecting a password entry does nothing (if it appears at all) 4. Close Chrome via Recents screen and open it again 5. Now autofill entries show up in the keyboard and work Rinse and repeat every time you have an issue.
GiteaMirror commented 2026-04-11 01:25:20 -05:00
Author
Owner
Copy Link

@emmaLP commented on GitHub (Sep 21, 2025):

Experiencing autofill issues with inline keyboard as well as with the chrome autofill integration.

The chrome autofill integration has never worked for me, so the just use the inline autofill keyboard suggestions.

For about the past 6 months the inline keyboard autofill has been very inconsistent or doesn't work at all.
Sometimes the option to unlock bitwarden doesn't show up within the keyboard, this is quite rare.
Other times when I have unlocked bitwarden (via the inline keyboard option), then clicking on the username and password you want to autofill just doesn't work for 95% of the time. I've tried 2 different keyboards(swiftkey and Samsung) and get the same result.

I have tried turning all the autofill options in the bitwarden app off and then back on again and that doesn't solve the problem.

Additional information:
Device: Samsung S22 Ultra
OS: Android 15
OneUI 7
Default keyboard: SwiftKey
Backup keyboard: Samsung
Bitwarden app version: © Bitwarden Inc. 2015-2025
Version: 2025.9.0 (20692)
📱 samsung SM-S908B 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.9-rc34@2bd4834b14d1e199aaa8a9ee4f0db812c27dba53
💻 build source: bitwarden/android/actions/runs/17498992515/attempts/1
🦀 SDK: 1.0.0-2887-7b5d9db2
🌩 Server: 2025.9.0 @ US

<!-- gh-comment-id:3315522172 --> @emmaLP commented on GitHub (Sep 21, 2025): Experiencing autofill issues with inline keyboard as well as with the chrome autofill integration. The chrome autofill integration has never worked for me, so the just use the inline autofill keyboard suggestions. For about the past 6 months the inline keyboard autofill has been very inconsistent or doesn't work at all. Sometimes the option to unlock bitwarden doesn't show up within the keyboard, this is quite rare. Other times when I have unlocked bitwarden (via the inline keyboard option), then clicking on the username and password you want to autofill just doesn't work for 95% of the time. I've tried 2 different keyboards(swiftkey and Samsung) and get the same result. I have tried turning all the autofill options in the bitwarden app off and then back on again and that doesn't solve the problem. Additional information: Device: Samsung S22 Ultra OS: Android 15 OneUI 7 Default keyboard: SwiftKey Backup keyboard: Samsung Bitwarden app version: © Bitwarden Inc. 2015-2025 Version: 2025.9.0 (20692) 📱 samsung SM-S908B 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.9-rc34@2bd4834b14d1e199aaa8a9ee4f0db812c27dba53 💻 build source: bitwarden/android/actions/runs/17498992515/attempts/1 🦀 SDK: 1.0.0-2887-7b5d9db2 🌩 Server: 2025.9.0 @ US
GiteaMirror commented 2026-04-11 01:25:21 -05:00
Author
Owner
Copy Link

@Ri-Dearg commented on GitHub (Sep 21, 2025):

This issue is most certainly related to this issue, which despite being closed, has not been fixed.

you can see in this comment and this comment from a maintainer that they made changes to how accessibility works, have broken it, made it less accessible and don't intend to fix the issue...

<!-- gh-comment-id:3315944399 --> @Ri-Dearg commented on GitHub (Sep 21, 2025): This issue is most certainly [related to this issue](https://github.com/bitwarden/android/issues/5341), which despite being closed, has not been fixed. [you can see in this comment](https://github.com/bitwarden/android/issues/5341#issuecomment-3251296773) and [this comment from a maintainer](https://github.com/bitwarden/android/issues/5341#issuecomment-3250975323) that they made changes to how accessibility works, have broken it, made it less accessible and don't intend to fix the issue...
GiteaMirror commented 2026-04-11 01:25:22 -05:00
Author
Owner
Copy Link

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

I would like to add some things here. First, there are two things that @dwbit shared first on the Community Forum (and probably also on Reddit etc.):

  • If you previously changed any browser autofill feature flags (chrome://flags, brave://flags…) – an older recommendation/necessity from 2023/2024 --, you may need to reset them now to the default flag settings to prevent autofill from breaking with the new Chrome autofill framework.

  • And there also is a new current bug on the Chromium browsers side – but on Chrome 141 BETA you can enable the following flag: #autofill-update-context-for-web-contents (chrome://flags). Eventually only browser updates will fix this bug.

There is also a new short guide about Autofill on Android, which collects all current "tips" etc.: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941/

<!-- gh-comment-id:3315989381 --> @pamperer562580892423 commented on GitHub (Sep 21, 2025): I would like to add some things here. First, there are two things that @dwbit shared first on the Community Forum (and probably also on Reddit etc.): - If you previously changed any browser autofill **feature flags** (chrome://flags, brave://flags…) – an older recommendation/necessity from 2023/2024 --, you may need to reset them now to the default flag settings to prevent autofill from breaking with the new Chrome autofill framework. - And there also is a new [current bug](https://issuetracker.google.com/issues/439553272) on the Chromium browsers side – but on Chrome 141 BETA you can enable the following flag: #autofill-update-context-for-web-contents (chrome://flags). Eventually only browser updates will fix this bug. There is also a new short guide about Autofill on Android, which collects all current "tips" etc.: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941/
GiteaMirror commented 2026-04-11 01:25:23 -05:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (Dec 11, 2025):

Adding another comment to bump this ticket (as one of the few that's actually still open!).

At various times I've encountered all of the issues reported by various people here and elsewhere. I mostly rely on the popup, because my preferred keyboard, the venerable "Hackers Keyboard", doesn't support inline autofill at all. But even the popup is incredibly hit and miss.

It's rare that anything works first time. I nearly always have to perform some combination of tapping in and out of fields, separately unlocking the BW app, and clicking the accessibility action tile, and then magically the popup might appear - despite me doing exactly the same as I had already done several times without success.

A newer issue is that autofill often fails to detect a field as fillable at all, even when forcing a screen scan by clicking the accessibility action tile (I just get the dreaded "No password fields detected", when I'm staring straight at one!). Given that many web sites and Android apps seem to be choosing to split the username and password onto separate pages, this is happening more frequently, and the result is that effectively autofill is broken entirely. I then have to juggle between the BW app and the login page (browser or Android app), performing a manual copy+paste for each of the fillable fields, often across multiple pages - dozens of taps to achieve what should be a single tap. And that's if the site/app doesn't abort the login as soon as it loses focus (yet another pointless "security" measure that seems to be becoming more common).

Pretty much all of these issues are, I assume, down to the built-in Android autofill service being poor. By comparison, the BW browser extension (on all platforms, including Android) works almost flawlessly, presumably because it has better visibility of the page's semantic structure, and doesn't have to rely on image pattern recognition. I understand the reasons for the BW Android team wanting to concentrate on a single implementation, but while the integrated service method is so woefully unfit for purpose, please can you reconsider supporting the browser extension on Android? I mostly use Firefox, but other browsers (at least those that support extensions) would also benefit. This would also restore two significant missing features: filling of cards would work again, and maybe PassKeys too, even on platforms (ie. slightly older Android versions) where Google doesn't allow "third party" providers.

<!-- gh-comment-id:3643546890 --> @richardb64 commented on GitHub (Dec 11, 2025): Adding another comment to bump this ticket (as one of the few that's actually still open!). At various times I've encountered all of the issues reported by various people here and elsewhere. I mostly rely on the popup, because my preferred keyboard, the venerable "Hackers Keyboard", doesn't support inline autofill at all. But even the popup is incredibly hit and miss. It's rare that anything works first time. I nearly always have to perform some combination of tapping in and out of fields, separately unlocking the BW app, and clicking the accessibility action tile, and then magically the popup _might_ appear - despite me doing exactly the same as I had already done several times without success. A newer issue is that autofill often fails to detect a field as fillable at all, even when forcing a screen scan by clicking the accessibility action tile (I just get the dreaded "No password fields detected", when I'm staring straight at one!). Given that many web sites and Android apps seem to be choosing to split the username and password onto separate pages, this is happening more frequently, and the result is that effectively autofill is broken entirely. I then have to juggle between the BW app and the login page (browser or Android app), performing a manual copy+paste for each of the fillable fields, often across multiple pages - dozens of taps to achieve what should be a single tap. And that's if the site/app doesn't abort the login as soon as it loses focus (yet another pointless "security" measure that seems to be becoming more common). Pretty much all of these issues are, I assume, down to the built-in Android autofill service being poor. By comparison, the BW _browser_ extension (on all platforms, including Android) works almost flawlessly, presumably because it has better visibility of the page's semantic structure, and doesn't have to rely on image pattern recognition. I understand the reasons for the BW Android team wanting to concentrate on a single implementation, but while the integrated service method is so woefully unfit for purpose, please can you reconsider supporting the browser extension on Android? I mostly use Firefox, but other browsers (at least those that support extensions) would also benefit. This would also restore two significant missing features: filling of cards would work again, and maybe PassKeys too, even on platforms (ie. slightly older Android versions) where Google doesn't allow "third party" providers.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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

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