Autofill isn&#39;t working on mobile (generally or for a specific site or app) #1282

GiteaMirror commented

@larena1 commented on GitHub (Jul 11, 2021):

@eliykat is there any news maybe? It's soon 3 months that "the Bitwarden team is actively working on" fixing the longstanding autofill issues, part of which been reported years ago but never cared about, and the commit history unfortunately does not indicate any progress so far.

@larena1 commented on GitHub (Jul 11, 2021): @eliykat is there any news maybe? It's soon 3 months that "the Bitwarden team is actively working on" fixing the longstanding autofill issues, part of which been reported years ago but never cared about, and the commit history unfortunately does not indicate any progress so far.

GiteaMirror commented

@ghost commented on GitHub (Jul 11, 2021):

I counted 62 referenced issues.

When my issue was closed this issue didn't even accurately reflect the problem that was described in the original issue.

I will admit, autofill has gotten better but I can't help but feel annoyed that so many people put in effort to help diagnose the problems with autofill only to be swept under the rug.

Edit: Why even bother going from a public issue tracker to a Google Form?

@ghost commented on GitHub (Jul 11, 2021): I counted 62 referenced issues. When my issue was closed this issue didn't even accurately reflect the problem that was described in the original issue. I will admit, autofill has gotten better but I can't help but feel annoyed that so many people put in effort to help diagnose the problems with autofill only to be swept under the rug. Edit: Why even bother going from a public issue tracker to a Google Form?

GiteaMirror commented

@tgreer-bw commented on GitHub (Jul 11, 2021):

Hi @douglasparker and @larena1 - thanks for your feedback here. I can confirm that this is an active research endeavor - no code commits yet, as we need to use a scalable and sustainable mechanism for this. We actually have brought additional roles into the engineering realm to assist with many of the autofill/autosave items.

@douglasparker we use the google sheet as a faster way to compare URLs, etc. than within comments on issues.

@tgreer-bw commented on GitHub (Jul 11, 2021): Hi @douglasparker and @larena1 - thanks for your feedback here. I can confirm that this is an active research endeavor - no code commits yet, as we need to use a scalable and sustainable mechanism for this. We actually have brought additional roles into the engineering realm to assist with many of the autofill/autosave items. @douglasparker we use the google sheet as a faster way to compare URLs, etc. than within comments on issues.

GiteaMirror commented

@puppykickr commented on GitHub (Jul 22, 2021):

As the Auto-Fill 'feature' has never, ever worked at all for me on any of my devices, I just don't use it.
Sure, at first it was very frustrating for me- but once I came to the conclusion that it does not work, will not ever work, and therefore is not really a feature at all- I was relieved of this irritation.

In fact, this is not a Bitwarden problem.
Auto-Fill never worked right for me even before Bitwarden was on any of my devices.

I just use the quick setting tile, and save the info I need to the clipboard (keyboard, not system) and type the other info.

Yes, it is a hassle.
But much less so than trying to get Auto-Fill to work.

@puppykickr commented on GitHub (Jul 22, 2021): As the Auto-Fill 'feature' has never, ever worked at all for me on any of my devices, I just don't use it. Sure, at first it was very frustrating for me- but once I came to the conclusion that it does not work, will not ever work, and therefore is not really a feature at all- I was relieved of this irritation. In fact, this is not a Bitwarden problem. Auto-Fill never worked right for me even before Bitwarden was on any of my devices. I just use the quick setting tile, and save the info I need to the clipboard (keyboard, not system) and type the other info. Yes, it is a hassle. But much less so than trying to get Auto-Fill to work.

GiteaMirror commented

@heiserhorn commented on GitHub (Aug 10, 2021):

Is there any time frame to improve the Auto-Fill behavior following the inputs provided in the google doc file?

@heiserhorn commented on GitHub (Aug 10, 2021): Is there any time frame to improve the Auto-Fill behavior following the inputs provided in the google doc file?

GiteaMirror commented

@geoffsterr commented on GitHub (Aug 11, 2021):

have you considered the possibility of an unknown malware capturing the password to certain apps? It kinda seems like the login details are getting captured in transit from vault to the certain app. I've run lots of scans with many products but well no can detect Pegasus yet only look for traces. I have reason to believe my device has been targeted by someone.
I've submitted the Google Form just now with the details

@geoffsterr commented on GitHub (Aug 11, 2021): have you considered the possibility of an unknown malware capturing the password to certain apps? It kinda seems like the login details are getting captured in transit from vault to the certain app. I've run lots of scans with many products but well no can detect Pegasus yet only look for traces. I have reason to believe my device has been targeted by someone. I've submitted the Google Form just now with the details

GiteaMirror commented

@ghost commented on GitHub (Aug 11, 2021):

I have reason to believe my device has been targeted by someone.

If your device was compromised, all of your accounts would be compromised and you'd be well aware of that by now.

Bitwarden can't protect you from a device that is compromised.

@ghost commented on GitHub (Aug 11, 2021): > I have reason to believe my device has been targeted by someone. If your device was compromised, all of your accounts would be compromised and you'd be well aware of that by now. Bitwarden can't protect you from a device that is compromised.

GiteaMirror commented

@geoffsterr commented on GitHub (Aug 11, 2021):

hi well it's not quite as simple as that, and I don't recall asking anything about needing protection, I was simply giving the background and a possible area to look at as a cause
I thought was pretty simple to make out without your massive assumptions

@geoffsterr commented on GitHub (Aug 11, 2021): hi well it's not quite as simple as that, and I don't recall asking anything about needing protection, I was simply giving the background and a possible area to look at as a cause I thought was pretty simple to make out without your massive assumptions

GiteaMirror commented

@ghost commented on GitHub (Aug 11, 2021):

hi well it's not quite as simple as that, and I don't recall asking anything about needing protection, I was simply giving the background and a possible area to look at as a cause

It's most definitely not malware that is causing the autofill issues.

I thought was pretty simple to make out without your massive assumptions

Yeah, okay bud. 👍

@ghost commented on GitHub (Aug 11, 2021): > hi well it's not quite as simple as that, and I don't recall asking anything about needing protection, I was simply giving the background and a possible area to look at as a cause It's most definitely not malware that is causing the autofill issues. > I thought was pretty simple to make out without your massive assumptions Yeah, okay bud. 👍

GiteaMirror commented

@larena1 commented on GitHub (Aug 16, 2021):

@eliykat @Greenderella

Another month now and still no traces of any progress to be seen. Would you mind sharing the status with us? Autofill is not an overly complicated feature IMHO. In case of native Android autofill it's just parsing the view structure and feeding the right data back to the system.

For the most part it's working as it is but it'll always fill the password into the username field on sites where there's only a username field like Amazon eBay PayPal Microsoft etc and that there's no fallback in match detection to detect hostname when only the hostname is provided like through native Android autofill APIs but the entry has match detection set to starts with.

@larena1 commented on GitHub (Aug 16, 2021): @eliykat @Greenderella Another month now and still no traces of any progress to be seen. Would you mind sharing the status with us? Autofill is not an overly complicated feature IMHO. In case of native Android autofill it's just parsing the view structure and feeding the right data back to the system. For the most part it's working as it is but it'll always fill the password into the username field on sites where there's only a username field like Amazon eBay PayPal Microsoft etc and that there's no fallback in match detection to detect hostname when only the hostname is provided like through native Android autofill APIs but the entry has match detection set to starts with.

GiteaMirror commented

@yurividal commented on GitHub (Aug 23, 2021):

On Samsung browser, if you close Samsung browser (recents, swipe up) and relaunch it, bitwarden works and you get the inline autofill. It works for a while, and then after some minutes it stops again. So, it's definitely some sort of timer or timeout that is going on, that somehow kills the autofill service for the browser.

@yurividal commented on GitHub (Aug 23, 2021): On Samsung browser, if you close Samsung browser (recents, swipe up) and relaunch it, bitwarden works and you get the inline autofill. **It works for a while, and then after some minutes it stops again**. So, it's definitely some sort of timer or timeout that is going on, that somehow kills the autofill service for the browser.

GiteaMirror commented

@cstrouse commented on GitHub (Aug 26, 2021):

Autofill is working on Android 10 devices and I've only been running into it not filling forms sporadically since upgrading my M1 Macbook Air to build 21A5304g of the Monterrey beta and my phone to build 19A5325f of the iOS 15 beta. The failures are occuring with the browser extensions for Safari, Chrome, and Firefox on macOS and iOS. When I describe the issue as sporadic I mean that it stops working for every site for a period of time (sometimes hours but this most recent autofill failure has been going on for nearly a week now). I'm applying the 15 beta 7 update to iOS this morning and hoping that whatever they changed is resolved as they work on the new browser extension support for mobile Safari, etc. Will advise.

UPDATE: Updating to 15 beta (19A5337a) seems to have resolved the autofill problem.

@cstrouse commented on GitHub (Aug 26, 2021): Autofill is working on Android 10 devices and I've only been running into it not filling forms sporadically since upgrading my M1 Macbook Air to build 21A5304g of the Monterrey beta and my phone to build 19A5325f of the iOS 15 beta. The failures are occuring with the browser extensions for Safari, Chrome, and Firefox on macOS and iOS. When I describe the issue as sporadic I mean that it stops working for every site for a period of time (sometimes hours but this most recent autofill failure has been going on for nearly a week now). I'm applying the 15 beta 7 update to iOS this morning and hoping that whatever they changed is resolved as they work on the new browser extension support for mobile Safari, etc. Will advise. **UPDATE**: Updating to 15 beta (19A5337a) seems to have resolved the autofill problem.

GiteaMirror commented

@THEOCKID commented on GitHub (Sep 4, 2021):

@eliykat @Greenderella

Another month now and still no traces of any progress to be seen. Would you mind sharing the status with us? Autofill is not an overly complicated feature IMHO. In case of native Android autofill it's just parsing the view structure and feeding the right data back to the system.

For the most part it's working as it is but it'll always fill the password into the username field on sites where there's only a username field like Amazon eBay PayPal Microsoft etc and that there's no fallback in match detection to detect hostname when only the hostname is provided like through native Android autofill APIs but the entry has match detection set to starts with.
==============

I would say that Autofill is a wildly complicated feature, depending on 10's of items all working at the same time to have a successfull 'fill.

Truth be told, I've used bitwarden for years and have loved it. Recently, I've tried "straying" to other PW managers (e.g. 1password, Keeper). They have more pleasing interfaces, and I just wanted to see what was out there. Well, I can tell you I'm back to Bitwarden, and I'll probably "stray" in 3-5 years again to test the waters.

Bitwarden, ,while not perfect, is in my opinion the top in terms of functionality. With autofill, yes, it doesnt always pop up perfectly, and/or doesn't make the right pick from my vault, BUT I always have the access to BW via the QuickTiles, and can quickly get the Username/Password/TOTP that I need, and those things can't be said for Keeper or 1PW etc. Those other apps: if they don't get a perfect match with your vault records, pow, you get nothing. NOTHING. BW has multiple redundancies / paths at hand.

With BW, I know that I have multiple routes to get my info that i need. It either (a) works and pops up the autofill button and (a1) gives me the correct info or (a2) I can pick from the list of comparable logins or (1c) I can choose to search my entire vault and copy and paste manually OR (b) doesn't pop up and I can (b1) go to the QuickTiles and pick either (b2) Auto-fill or (b3) My Vault and get my info that way (I don't find the Auto-fill quicktile to work that frequently, but I still try it).

I want to thank @kspearrin and @tgreer-bw et al for their continued improvements with the app, and I've learned to be patient with the process. Oh, and btw, nice new avatar @kspearrin (although you did look like quite the jet pilot in your prior one)

@THEOCKID commented on GitHub (Sep 4, 2021): > @eliykat @Greenderella > > Another month now and still no traces of any progress to be seen. Would you mind sharing the status with us? Autofill is not an overly complicated feature IMHO. In case of native Android autofill it's just parsing the view structure and feeding the right data back to the system. > > For the most part it's working as it is but it'll always fill the password into the username field on sites where there's only a username field like Amazon eBay PayPal Microsoft etc and that there's no fallback in match detection to detect hostname when only the hostname is provided like through native Android autofill APIs but the entry has match detection set to starts with. ============== I would say that Autofill is a *wildly* complicated feature, depending on 10's of items all working at the same time to have a successfull 'fill. Truth be told, I've used bitwarden for years and have loved it. Recently, I've tried "straying" to other PW managers (e.g. 1password, Keeper). They have more pleasing interfaces, and I just wanted to see what was out there. Well, I can tell you I'm back to Bitwarden, and I'll probably "stray" in 3-5 years again to test the waters. Bitwarden, ,while not perfect, is in my opinion the top in terms of functionality. With autofill, yes, it doesnt always pop up perfectly, and/or doesn't make the right pick from my vault, BUT I always have the access to BW via the QuickTiles, and can quickly get the Username/Password/TOTP that I need, and those things can't be said for Keeper or 1PW etc. Those other apps: if they don't get a perfect match with your vault records, pow, you get nothing. NOTHING. BW has multiple redundancies / paths at hand. With BW, I know that I have multiple routes to get my info that i need. It either (a) works and pops up the autofill button and (a1) gives me the correct info or (a2) I can pick from the list of comparable logins or (1c) I can choose to search my entire vault and copy and paste manually OR (b) doesn't pop up and I can (b1) go to the QuickTiles and pick either (b2) Auto-fill or (b3) My Vault and get my info that way (I don't find the Auto-fill quicktile to work that frequently, but I still try it). I want to thank @kspearrin and @tgreer-bw et al for their continued improvements with the app, and I've learned to be patient with the process. Oh, and btw, nice new avatar @kspearrin (although you did look like quite the jet pilot in your prior one)

GiteaMirror commented

@AnthillSudoku commented on GitHub (Sep 30, 2021):

Hi,
please do not take this as impoliteness to your team.

KepassDX password manager has no issue with autofill in my Android 10 except that it does not copy OTP.
Since it is opensource, do you believe is worth a look how they are doing it?

Thanks

@AnthillSudoku commented on GitHub (Sep 30, 2021): Hi, please do not take this as impoliteness to your team. [KepassDX](https://github.com/Kunzisoft/KeePassDX) password manager has no issue with autofill in my Android 10 except that it does not copy OTP. Since it is opensource, do you believe is worth a look how they are doing it? Thanks

GiteaMirror commented

@yurividal commented on GitHub (Oct 8, 2021):

I have recently updated my Samsung Galaxy s21 to android 12 Beta (OneUI 4) and i can confirm that inline autofill has started to work as intended! Seems to work every time, using Samsung browser or chrome. No more timeouts (as of yet. It's been 3 days)

@yurividal commented on GitHub (Oct 8, 2021): I have recently updated my Samsung Galaxy s21 to android 12 Beta (OneUI 4) and i can confirm that inline autofill has started to work as intended! Seems to work every time, using Samsung browser or chrome. No more timeouts (as of yet. It's been 3 days)

GiteaMirror commented

@yurividal commented on GitHub (Oct 27, 2021):

I have recently updated my Samsung Galaxy s21 to android 12 Beta (OneUI 4) and i can confirm that inline autofill has started to work as intended! Seems to work every time, using Samsung browser or chrome. No more timeouts (as of yet. It's been 3 days)

Unfortunately, after a couple of days the same behavior is back. Autofill works for a while and then it stops. The only way to get it back is to kill the browser app and reopen it, Then it works again for a while. This is SO ANNOYING!!!

@yurividal commented on GitHub (Oct 27, 2021): > I have recently updated my Samsung Galaxy s21 to android 12 Beta (OneUI 4) and i can confirm that inline autofill has started to work as intended! Seems to work every time, using Samsung browser or chrome. No more timeouts (as of yet. It's been 3 days) Unfortunately, after a couple of days the same behavior is back. Autofill works for a while and then it stops. The only way to get it back is to kill the browser app and reopen it, Then it works again for a while. This is SO ANNOYING!!!

GiteaMirror commented

@larena1 commented on GitHub (Nov 2, 2021):

More than half a year now and nothing but empty words so far. I was kind of expecting this having seen how issues were being dealt with (or not dealt with at all) in recent years but had a little hope nonetheless.

@larena1 commented on GitHub (Nov 2, 2021): More than half a year now and nothing but empty words so far. I was kind of expecting this having seen how issues were being dealt with (or not dealt with at all) in recent years but had a little hope nonetheless.

GiteaMirror commented

@ghost commented on GitHub (Nov 2, 2021):

Yeah, I was hoping to see some improvements in this area.

Can anyone on the Bitwarden team provide an update?

@ghost commented on GitHub (Nov 2, 2021): Yeah, I was hoping to see some improvements in this area. Can anyone on the Bitwarden team provide an update?

GiteaMirror commented

@yurividal commented on GitHub (Nov 2, 2021):

More than half a year now and nothing but empty words so far. I was kind of expecting this having seen how issues were being dealt with (or not dealt with at all) in recent years but had a little hope nonetheless.

This seems to be a very complex bug, that involves not only the password manager but also the browsers and maybe even the keyboards.
But, I agree... it is frustrating indeed to have such an issue on a crucial part of the app, and still persist after more than 1 year...

@yurividal commented on GitHub (Nov 2, 2021): > More than half a year now and nothing but empty words so far. I was kind of expecting this having seen how issues were being dealt with (or not dealt with at all) in recent years but had a little hope nonetheless. This seems to be a very complex bug, that involves not only the password manager but also the browsers and maybe even the keyboards. But, I agree... it is frustrating indeed to have such an issue on a crucial part of the app, and still persist after more than 1 year...

GiteaMirror commented

@larena1 commented on GitHub (Nov 2, 2021):

More than half a year now and nothing but empty words so far. I was kind of expecting this having seen how issues were being dealt with (or not dealt with at all) in recent years but had a little hope nonetheless.

This seems to be a very complex bug, that involves not only the password manager but also the browsers and maybe even the keyboards. But, I agree... it is frustrating indeed to have such an issue on a crucial part of the app, and still persist after more than 1 year...

It is not that complex at all. It's just that apparently nobody is working on it and that the last official reply was soon 4 months ago.

@larena1 commented on GitHub (Nov 2, 2021): > > More than half a year now and nothing but empty words so far. I was kind of expecting this having seen how issues were being dealt with (or not dealt with at all) in recent years but had a little hope nonetheless. > > This seems to be a very complex bug, that involves not only the password manager but also the browsers and maybe even the keyboards. But, I agree... it is frustrating indeed to have such an issue on a crucial part of the app, and still persist after more than 1 year... It is not that complex at all. It's just that apparently nobody is working on it and that the last official reply was soon 4 months ago.

GiteaMirror commented

@THEOCKID commented on GitHub (Nov 2, 2021):

So I got a new Pixel 6 Pro, and had issues, but I've figured out how to get it to work and it hasn't failed me in >2 days (and I use BW a TON!):

Go into BW on your phone

Go to Auto-fill Services, and turn off everything: 1st Use Inline Autofill, then Auto-fill Service. Then Use Draw-Over, then Use Accessibility

Quit BW

Close all apps

Restart phone

Upon restart, run BW and re-enable the 4 options above.

Seems to be working for me. If needed, before you restart, you could go to Apps (on Android) and open BW and Clear Cache, and could even Clear Data, then restart, then re-enable the 4 options.

Please let me know if this helped.

@THEOCKID commented on GitHub (Nov 2, 2021): So I got a new Pixel 6 Pro, and had issues, but I've figured out how to get it to work and it hasn't failed me in >2 days (and I use BW a TON!): # Go into BW on your phone # Go to Auto-fill Services, and turn off everything: 1st Use Inline Autofill, then Auto-fill Service. Then Use Draw-Over, then Use Accessibility # Quit BW # Close all apps # Restart phone Upon restart, run BW and re-enable the 4 options above. Seems to be working for me. If needed, before you restart, you could go to Apps (on Android) and open BW and Clear Cache, and could even Clear Data, then restart, then re-enable the 4 options. Please let me know if this helped.

GiteaMirror commented

@THEOCKID commented on GitHub (Nov 2, 2021):

@larena1 pls chill a little. These guys aren't some big mega-company. And what does BW cost you? $10 a year? Let's have some empathy here.

And BTW, I have tried Keeper, having thought of jumping ship from BW. It's pretty, but also not nearly as functional as BW. I know, BW isn't for everyone (I'm a function over form guy), but it's pretty solid and I've been using it for .... 6+ years now?

@larena1 pls try my technique above, lemme know if it works for you

@THEOCKID commented on GitHub (Nov 2, 2021): @larena1 pls chill a little. These guys aren't some big mega-company. And what does BW cost you? $10 a year? Let's have some empathy here. And BTW, I have tried Keeper, having thought of jumping ship from BW. It's pretty, but also not nearly as functional as BW. I know, BW isn't for everyone (I'm a function over form guy), but it's pretty solid and I've been using it for .... 6+ years now? @larena1 pls try my technique above, lemme know if it works for you

GiteaMirror commented

@yurividal commented on GitHub (Nov 2, 2021):

So I got a new Pixel 6 Pro, and had issues, but I've figured out how to get it to work and it hasn't failed me in >2 days (and I use BW a TON!):

Go into BW on your phone

Go to Auto-fill Services, and turn off everything: 1st Use Inline Autofill, then Auto-fill Service. Then Use Draw-Over, then Use Accessibility

Quit BW

Close all apps

Restart phone

Upon restart, run BW and re-enable the 4 options above.

Seems to be working for me. If needed, before you restart, you could go to Apps (on Android) and open BW and Clear Cache, and could even Clear Data, then restart, then re-enable the 4 options.

Please let me know if this helped.

The thing is that for android 11 and 12, we should NOT be using Draw over and accessibility. These are legacy methods that do not use the built-in auto-fill api.

Even if this is a workaround, it's not a valid one. The bitwarden team needs to look into what is causing the bitwarden autofill agent to go into sleep.

@yurividal commented on GitHub (Nov 2, 2021): > So I got a new Pixel 6 Pro, and had issues, but I've figured out how to get it to work and it hasn't failed me in >2 days (and I use BW a TON!): > > # Go into BW on your phone > # Go to Auto-fill Services, and turn off everything: 1st Use Inline Autofill, then Auto-fill Service. Then Use Draw-Over, then Use Accessibility > # Quit BW > # Close all apps > # Restart phone > Upon restart, run BW and re-enable the 4 options above. > > Seems to be working for me. If needed, before you restart, you could go to Apps (on Android) and open BW and Clear Cache, and could even Clear Data, then restart, then re-enable the 4 options. > > Please let me know if this helped. The thing is that for android 11 and 12, we should NOT be using Draw over and accessibility. These are legacy methods that do not use the built-in auto-fill api. Even if this is a workaround, it's not a valid one. The bitwarden team needs to look into what is causing the bitwarden autofill agent to go into sleep.

GiteaMirror commented

@larena1 commented on GitHub (Nov 2, 2021):

Autofill does work for the most part but there's issues like bitwarden filling the password into the username field on PayPal eBay Google login etc and little issues like https://github.com/bitwarden/mobile/issues/1509 that could be fixed easily... If anybody was working on it but that's not the case and it's a pity

@larena1 commented on GitHub (Nov 2, 2021): Autofill does work for the most part but there's issues like bitwarden filling the password into the username field on PayPal eBay Google login etc and little issues like https://github.com/bitwarden/mobile/issues/1509 that could be fixed easily... If anybody was working on it but that's not the case and it's a pity

GiteaMirror commented

@THEOCKID commented on GitHub (Nov 2, 2021):

OK, I've given you a method to get it to work, @yurividal . Maybe BW isn't for you. Try 1Password or LastPass, see how they work.

@larena1 : I'm not sure how you have determined that "(nobody is) working on it". @kspearrin and (sorry, forgot the other guys name) (@tgreer-bw , sorry) are on here all the time. As above, maybe a diff PW manager would be better for you. Putting negativity on this site may make you feel better, but it's really doing nothing to forward the cause for BW.

let's buck up, campers. If you wanna help, help. If you wanna complain, then be pleasant/positiive, or just shove off.

@THEOCKID commented on GitHub (Nov 2, 2021): OK, I've given you a method to get it to work, @yurividal . Maybe BW isn't for you. Try 1Password or LastPass, see how they work. @larena1 : I'm not sure how you have determined that "(nobody is) working on it". @kspearrin and (sorry, forgot the other guys name) (@tgreer-bw , sorry) are on here all the time. As above, maybe a diff PW manager would be better for you. Putting negativity on this site may make you feel better, but it's really doing nothing to forward the cause for BW. let's buck up, campers. If you wanna help, help. If you wanna complain, then be pleasant/positiive, or just shove off.

GiteaMirror commented

2025-11-26 22:43:42 -06:00

@heiserhorn commented on GitHub (Nov 7, 2021):

I personally stopped using BW because of the Android performance. Inline Autofill not working reliably. Some sites not recognized at all. I appreciate the workarounds but satisfying my needs at the moment. Will come back in the future to see where we stand on this.

@heiserhorn commented on GitHub (Nov 7, 2021): I personally stopped using BW because of the Android performance. Inline Autofill not working reliably. Some sites not recognized at all. I appreciate the workarounds but satisfying my needs at the moment. Will come back in the future to see where we stand on this.

GiteaMirror commented

@olfek commented on GitHub (Nov 7, 2021):

@heiserhorn What are you using instead? I'm planning to do the same.

@olfek commented on GitHub (Nov 7, 2021): @heiserhorn What are you using instead? I'm planning to do the same.

GiteaMirror commented

2025-11-26 22:43:42 -06:00

@heiserhorn commented on GitHub (Nov 7, 2021):

@olfek I am trying a few and have not decided yet.

@heiserhorn commented on GitHub (Nov 7, 2021): @olfek I am trying a few and have not decided yet.

GiteaMirror commented

2025-11-26 22:43:42 -06:00

@julian-alarcon commented on GitHub (Dec 4, 2021):

I found a workaround for Firefox here
https://github.com/mozilla-mobile/fenix/issues/20987#issuecomment-904772802

Workaround for this:
1- tap to password area
2- press to three dot to open Firefox menu
3- press outside of menu to close it

Also, there is bugzilla report https://bugzilla.mozilla.org/show_bug.cgi?id=1693152

This is also reported in issue https://github.com/bitwarden/mobile/issues/1479

@julian-alarcon commented on GitHub (Dec 4, 2021): I found a workaround for Firefox here https://github.com/mozilla-mobile/fenix/issues/20987#issuecomment-904772802 Workaround for this: 1- tap to password area 2- press to three dot to open Firefox menu 3- press outside of menu to close it Also, there is bugzilla report https://bugzilla.mozilla.org/show_bug.cgi?id=1693152 This is also reported in issue https://github.com/bitwarden/mobile/issues/1479

GiteaMirror commented

2025-11-26 22:43:43 -06:00

@ghost commented on GitHub (Dec 5, 2021):

https://myid.telstra.com/identity/as/authorization.oauth2?redirect_uri=com.telstra.mobile.android.mytelstra%3A%2F%2Foauth2redirect&client_id=mytelstra-mobile-android&response_type=code&prompt=login&state=jh7Hle0JfHGCCk5S3YuT4g&scope=openid%20app.mytelstra.mobile%20m2w&code_challenge=Ppa1bnRLC6Ei9ig_rmWTooxv6BurGm-V_PccX-SGnlE&code_challenge_method=S256

The Username box does not get detected by Bitwarden at all until you enter the username, and then tap continue to reveal the password box.

@ghost commented on GitHub (Dec 5, 2021): https://myid.telstra.com/identity/as/authorization.oauth2?redirect_uri=com.telstra.mobile.android.mytelstra%3A%2F%2Foauth2redirect&client_id=mytelstra-mobile-android&response_type=code&prompt=login&state=jh7Hle0JfHGCCk5S3YuT4g&scope=openid%20app.mytelstra.mobile%20m2w&code_challenge=Ppa1bnRLC6Ei9ig_rmWTooxv6BurGm-V_PccX-SGnlE&code_challenge_method=S256 The Username box does not get detected by Bitwarden at all until you enter the username, and then tap continue to reveal the password box.

GiteaMirror commented

2025-11-26 22:43:43 -06:00

@novocaiin commented on GitHub (Dec 18, 2021):

OK, I've given you a method to get it to work, @yurividal . Maybe BW isn't for you. Try 1Password or LastPass, see how they work.

I don't want to give all my passwords to yet another party.

@novocaiin commented on GitHub (Dec 18, 2021): > OK, I've given you a method to get it to work, @yurividal . Maybe BW isn't for you. Try 1Password or LastPass, see how they work. I don't want to give all my passwords to yet another party.

GiteaMirror commented

2025-11-26 22:43:43 -06:00

@huangtaizia commented on GitHub (Dec 22, 2021):

When I open encrypted pdf file by pdf viewer of Google Drive, the BW dialog is appeared and closed immediately, cannot taps on to open BW to select the password saved. I thinking about that BW dialog cannot draw-over any dialog of the others application

@huangtaizia commented on GitHub (Dec 22, 2021): When I open encrypted pdf file by pdf viewer of Google Drive, the BW dialog is appeared and closed immediately, cannot taps on to open BW to select the password saved. I thinking about that BW dialog cannot draw-over any dialog of the others application

GiteaMirror commented

@toxic0berliner commented on GitHub (Jan 30, 2022):

I find autofill generally works unless for the sites where I changed the url comparison method to "exact". Can maybe someone look into it, I don't know how to check if the browser passes à wrong url, or if bitwarden isn't able to do the comparison, but I have confirmed that the url is exactly the same but bitwarden isn't showing the item as result.
Even searching manually in bw app it doesn't check. My url is set to exact and looks like https://organizr.example.com/#mytab
Works perfectly in Firefox extension on windows but not in the android app

@toxic0berliner commented on GitHub (Jan 30, 2022): I find autofill generally works unless for the sites where I changed the url comparison method to "exact". Can maybe someone look into it, I don't know how to check if the browser passes à wrong url, or if bitwarden isn't able to do the comparison, but I have confirmed that the url is exactly the same but bitwarden isn't showing the item as result. Even searching manually in bw app it doesn't check. My url is set to exact and looks like https://organizr.example.com/#mytab Works perfectly in Firefox extension on windows but not in the android app

GiteaMirror commented

@ghost commented on GitHub (Feb 10, 2022):

It feels like autofill is only getting worse with each major update to Android...

It's working less than half of the time for me on my Samsung Galaxy S21 Ultra running Android 12.

@ghost commented on GitHub (Feb 10, 2022): It feels like autofill is only getting worse with each major update to Android... It's working less than half of the time for me on my Samsung Galaxy S21 Ultra running Android 12.

GiteaMirror commented

@larena1 commented on GitHub (Feb 10, 2022):

It feels like autofill is only getting worse with each major update to Android...

It's working less than half of the time for me on my Samsung Galaxy S21 Ultra running Android 12.

Did you give other apps a try to see if the issues are specific to Bitwarden or your device / OS?

But yeah it's been more than 9 months since the big announcement that they're actively working on autofill and yet results still remain to be seen and there has been radio silence for more than six months already.

@larena1 commented on GitHub (Feb 10, 2022): > It feels like autofill is only getting worse with each major update to Android... > > It's working less than half of the time for me on my Samsung Galaxy S21 Ultra running Android 12. Did you give other apps a try to see if the issues are specific to Bitwarden or your device / OS? But yeah it's been more than 9 months since the big announcement that they're actively working on autofill and yet results still remain to be seen and there has been radio silence for more than six months already.

GiteaMirror commented

@THEOCKID commented on GitHub (Feb 10, 2022):

I've been a huge bitwarden proponent, but even I am finally getting tired of manually filling fields. Sorry, it's become a pain in the ass. So I'm going back to trialing Keeper and 1password. Maybe BW is more focused on their commercial/enterprise customers. Not sure. Hell, I'm not even sure they're reading GitHub comments. #disappointed

@THEOCKID commented on GitHub (Feb 10, 2022): I've been a huge bitwarden proponent, but even I am finally getting tired of manually filling fields. Sorry, it's become a pain in the ass. So I'm going back to trialing Keeper and 1password. Maybe BW is more focused on their commercial/enterprise customers. Not sure. Hell, I'm not even sure they're reading GitHub comments. #disappointed

GiteaMirror commented

@ghost commented on GitHub (Feb 10, 2022):

It feels like autofill is only getting worse with each major update to Android...

It's working less than half of the time for me on my Samsung Galaxy S21 Ultra running Android 12.

Did you give other apps a try to see if the issues are specific to Bitwarden or your device / OS?

I took a look at 1Password again, and the autofill API works flawlessly every time.

It works so well that I've barely used my annual family subscription with Bitwarden, and I am eager to migrate over right away.

But yeah it's been more than 9 months since the big announcement that they're actively working on autofill and yet results still remain to be seen and there has been radio silence for more than six months already.

Yeah, I didn't realize how bad autofill had gotten with Bitwarden until I gave 1Password a try again.

The level of support by the Bitwarden team has been horrible, too. The lack of communication speaks for itself.

I'm also a huge Bitwarden supporter. I self host Bitwarden as well, and as much as I love open source software, I can't continue to support software that is broken on a fundamental level.

I'm sure that I am far from being the only one who is sick and tired of switching apps to log in to services.

@ghost commented on GitHub (Feb 10, 2022): > > It feels like autofill is only getting worse with each major update to Android... > > > > It's working less than half of the time for me on my Samsung Galaxy S21 Ultra running Android 12. > > Did you give other apps a try to see if the issues are specific to Bitwarden or your device / OS? I took a look at 1Password again, and the autofill API works flawlessly every time. It works so well that I've barely used my annual family subscription with Bitwarden, and I am eager to migrate over right away. > But yeah it's been more than 9 months since the big announcement that they're actively working on autofill and yet results still remain to be seen and there has been radio silence for more than six months already. Yeah, I didn't realize how bad autofill had gotten with Bitwarden until I gave 1Password a try again. The level of support by the Bitwarden team has been horrible, too. The lack of communication speaks for itself. I'm also a huge Bitwarden supporter. I self host Bitwarden as well, and as much as I love open source software, I can't continue to support software that is broken on a fundamental level. I'm sure that I am far from being the only one who is sick and tired of switching apps to log in to services.

GiteaMirror commented

@vvolkgang commented on GitHub (Feb 11, 2022):

Hey everyone! We recently made some improvements to the Android Accessibility Service fixing issues that previously impacted our autofill functionality, it's included in our recent release, currently in each platform store reviewing process.

We failed to communicate that here and for that I'm truly sorry. The team has been actively looking for ways to improve Autofill in Android, some of the ideas we tried failed to accommodate the whole range of Android versions + devices we support but, just wanted to let everyone know that we're still going at it and trying to improve.

Thanks for your feedback and support, let me know if the new release improves this.

@vvolkgang commented on GitHub (Feb 11, 2022): Hey everyone! We recently made some improvements to the Android Accessibility Service fixing issues that previously impacted our autofill functionality, it's included in our [recent release](https://github.com/bitwarden/mobile/releases/tag/v2.16.1), currently in each platform store reviewing process. We failed to communicate that here and for that I'm truly sorry. The team has been actively looking for ways to improve Autofill in Android, some of the ideas we tried failed to accommodate the whole range of Android versions + devices we support but, just wanted to let everyone know that we're still going at it and trying to improve. Thanks for your feedback and support, let me know if the new release improves this.

GiteaMirror commented

@THEOCKID commented on GitHub (Feb 11, 2022):

this may be a case of too little too late. I tried Keeper, eh, not great, but 1 Password seems to be fitting the bill. Autofill actually works (shocking!). GUI superior as well. I actually upgraded to their business version as it allows multiple 2FA yubikeys (The basic version allows for a TOTP and a physical key).

Dang BW. It's been a long ride. I'll check back in a year or so.

@THEOCKID commented on GitHub (Feb 11, 2022): this may be a case of too little too late. I tried Keeper, eh, not great, but 1 Password seems to be fitting the bill. Autofill actually works (shocking!). GUI superior as well. I actually upgraded to their business version as it allows multiple 2FA yubikeys (The basic version allows for a TOTP and a physical key). Dang BW. It's been a long ride. I'll check back in a year or so.

GiteaMirror commented

@yurividal commented on GitHub (Feb 11, 2022):

Hey everyone! We recently made some improvements to the Android Accessibility Service fixing issues that previously impacted our autofill functionality, it's included in our recent release, currently in each platform store reviewing process.

We failed to communicate that here and for that I'm truly sorry. The team has been actively looking for ways to improve Autofill in Android, some of the ideas we tried failed to accommodate the whole range of Android versions + devices we support but, just wanted to let everyone know that we're still going at it and trying to improve.

Thanks for your feedback and support, let me know if the new release improves this.

Does this mean we need to use the accessibility service? Its supposed to be a legacy method, replaced by the autofill API since Android 11

@yurividal commented on GitHub (Feb 11, 2022): > Hey everyone! We recently made some improvements to the Android Accessibility Service fixing issues that previously impacted our autofill functionality, it's included in our [recent release](https://github.com/bitwarden/mobile/releases/tag/v2.16.1), currently in each platform store reviewing process. > > We failed to communicate that here and for that I'm truly sorry. The team has been actively looking for ways to improve Autofill in Android, some of the ideas we tried failed to accommodate the whole range of Android versions + devices we support but, just wanted to let everyone know that we're still going at it and trying to improve. > > Thanks for your feedback and support, let me know if the new release improves this. Does this mean we need to use the accessibility service? Its supposed to be a legacy method, replaced by the autofill API since Android 11

GiteaMirror commented

https://github.com/bitwarden/mobile/commits/master/src/Android/Autofill

@larena1 commented on GitHub (Feb 11, 2022):

Looking at the history, apart from adding new browsers' app ids to the list of supported browsers, there is only 1 PR that included functional changes of autofill handling.

52024109f7

And that does only affect the save prompt for credentials so there seem to be no improvements at all to reliability and quality of autofill itself unfortunately.

@vvolkgang thanks though for at least giving us an update

EDIT:

https://github.com/bitwarden/mobile/pull/1673

There was indeed another PR targeting Accessibility Service, which should now work correctly on Android 11+.

What still remains though is issues like https://github.com/bitwarden/mobile/issues/1509 and that it will fill the password into username fields when logging in to Google, Microsoft, eBay, Paypal etc..

@larena1 commented on GitHub (Feb 11, 2022): https://github.com/bitwarden/mobile/commits/master/src/Android/Autofill Looking at the history, apart from adding new browsers' app ids to the list of supported browsers, there is only 1 PR that included functional changes of autofill handling. https://github.com/bitwarden/mobile/commit/52024109f7bfd6ae36c6273d03076242c99fd63f And that does only affect the save prompt for credentials so there seem to be no improvements at all to reliability and quality of autofill itself unfortunately. @vvolkgang thanks though for at least giving us an update EDIT: https://github.com/bitwarden/mobile/pull/1673 There was indeed another PR targeting Accessibility Service, which should now work correctly on Android 11+. What still remains though is issues like https://github.com/bitwarden/mobile/issues/1509 and that it will fill the password into username fields when logging in to Google, Microsoft, eBay, Paypal etc..

GiteaMirror commented

@JoshuaGloriod commented on GitHub (Feb 16, 2022):

You guys probably already know, but I've found all troubles with Bitwarden went away with following DKMA's recommended settings. Mentioning just in case.

As seen in this issue https://github.com/urbandroid-team/dont-kill-my-app/issues/307#issue-837495424

I still have the mentioned problem with fields, but Bitwarden now does recognize when it should autofill now. I've looked into that a bit, but not confident on the exact reason yet.

By the way, I highly recommend following their advice, it made battery life much better as well.

@JoshuaGloriod commented on GitHub (Feb 16, 2022): You guys probably already know, but I've found all troubles with Bitwarden went away with following DKMA's recommended settings. Mentioning just in case. As seen in this issue https://github.com/urbandroid-team/dont-kill-my-app/issues/307#issue-837495424 I still have the mentioned problem with fields, but Bitwarden now does recognize when it should autofill now. I've looked into that a bit, but not confident on the exact reason yet. By the way, I highly recommend following their advice, it made battery life much better as well.

GiteaMirror commented

@bill-mcgonigle commented on GitHub (Mar 16, 2022):

This has been bugging me for a long time (Android 11, LineageOS) and by following a few threads here I believe I have isolated my problem to "Battery Manager". After turning it off I don't have to constantly relaunch Bitwarden to get autofill.

I do not see Bitwarden using even 1% of the battery in the usage stats (it's too low to show up) so I don't know /why/ it was getting killed. If there's something that could be done programmatically or in the manifest to avoid being reaped by Battery Manager that might help. In theory I should not have to turn it off to use Bitwarden—one presumes that feature isn't fundamentally incompatible with autofill services.
n.b. I already had Bitwarden set to 'not optimized' so this is something different.

@bill-mcgonigle commented on GitHub (Mar 16, 2022): This has been bugging me for a long time (Android 11, LineageOS) and by following a few threads here I believe I have isolated my problem to "Battery Manager". After turning it off I don't have to constantly relaunch Bitwarden to get autofill. ![Screenshot_20220316-170220_Settings~2](https://user-images.githubusercontent.com/880256/158690883-b9efc871-9622-463d-9335-f07b7fc48aa2.png) I do not see Bitwarden using even 1% of the battery in the usage stats (it's too low to show up) so I don't know /why/ it was getting killed. If there's something that could be done programmatically or in the manifest to avoid being reaped by Battery Manager that might help. In theory I should not have to turn it off to use Bitwarden—one presumes that feature isn't fundamentally incompatible with autofill services. n.b. I already had Bitwarden set to 'not optimized' so this is something different.

GiteaMirror commented

@ghost commented on GitHub (Mar 18, 2022):

iodé Browser does not autofill as it should.
com.iode.firefox

@ghost commented on GitHub (Mar 18, 2022): iodé Browser does not autofill as it should. com.iode.firefox

GiteaMirror commented

@syed-ammar commented on GitHub (Mar 30, 2022):

I had the problem for Spotify and Formula1 android app. Enabling Accessibility worked for Spotify app, but for Formula1 it is asking me to create new item even though i have that on my list

@syed-ammar commented on GitHub (Mar 30, 2022): I had the problem for Spotify and Formula1 android app. Enabling Accessibility worked for Spotify app, but for Formula1 it is asking me to create new item even though i have that on my list

GiteaMirror commented

@brotaxt commented on GitHub (Apr 2, 2022):

This has been bugging me for a long time (Android 11, LineageOS) and by following a few threads here I believe I have isolated my problem to "Battery Manager". After turning it off I don't have to constantly relaunch Bitwarden to get autofill.

I do not see Bitwarden using even 1% of the battery in the usage stats (it's too low to show up) so I don't know /why/ it was getting killed. If there's something that could be done programmatically or in the manifest to avoid being reaped by Battery Manager that might help. In theory I should not have to turn it off to use Bitwarden—one presumes that feature isn't fundamentally incompatible with autofill services. n.b. I already had Bitwarden set to 'not optimized' so this is something different.

This is exactly what I did and I couldn't recognize most of the issues that are reported here.

@brotaxt commented on GitHub (Apr 2, 2022): > This has been bugging me for a long time (Android 11, LineageOS) and by following a few threads here I believe I have isolated my problem to "Battery Manager". After turning it off I don't have to constantly relaunch Bitwarden to get autofill. ![Screenshot_20220316-170220_Settings~2](https://user-images.githubusercontent.com/880256/158690883-b9efc871-9622-463d-9335-f07b7fc48aa2.png) > > I do not see Bitwarden using even 1% of the battery in the usage stats (it's too low to show up) so I don't know /why/ it was getting killed. If there's something that could be done programmatically or in the manifest to avoid being reaped by Battery Manager that might help. In theory I should not have to turn it off to use Bitwarden—one presumes that feature isn't fundamentally incompatible with autofill services. n.b. I already had Bitwarden set to 'not optimized' so this is something different. This is exactly what I did and I couldn't recognize most of the issues that are reported here.

GiteaMirror commented

@THEOCKID commented on GitHub (Apr 2, 2022):

Hey! Laughing at myself cause the recent post got me to look at Settings:Apps:Bitwarden:Battery and lo and behold ... I wasn't unrestricted! Damn you Samsung! Now I fixed it and will see how it goes! Thanks everyone!

@THEOCKID commented on GitHub (Apr 2, 2022): Hey! Laughing at myself cause the recent post got me to look at Settings:Apps:Bitwarden:Battery and lo and behold ... I wasn't unrestricted! Damn you Samsung! Now I fixed it and will see how it goes! Thanks everyone! ![3414](https://user-images.githubusercontent.com/54771478/161379496-630a631f-7402-4f09-a10a-8b04e84e10fb.jpg)

GiteaMirror commented

@ghost commented on GitHub (Apr 2, 2022):

For what it’s worth, that didn’t fix it for me either. I always disable battery optimization for Bitwarden the moment I get a new phone and the issues persist.

I just switched to iPhone and all of my issues have been resolved. I’m no longer interested in dealing with bugs with the autofill API.

Google seems to ignore major bugs in their issue tracker for years. I’m a huge android fan but I’ve recently made the decision to completely switch ecosystems.

@ghost commented on GitHub (Apr 2, 2022): For what it’s worth, that didn’t fix it for me either. I always disable battery optimization for Bitwarden the moment I get a new phone and the issues persist. I just switched to iPhone and all of my issues have been resolved. I’m no longer interested in dealing with bugs with the autofill API. Google seems to ignore major bugs in their issue tracker for years. I’m a huge android fan but I’ve recently made the decision to completely switch ecosystems.

GiteaMirror commented

[Bug 1770010]: Autofill fails, when I need to unlock bitwarden.

@MrPeanut12 commented on GitHub (May 24, 2022):

For anyone using Firefox Nightly on Android, a bug has been resolved which fixed autofill for me (using Android 9).

@MrPeanut12 commented on GitHub (May 24, 2022): For anyone using Firefox Nightly on Android, a bug has been resolved which fixed autofill for me (using Android 9). [[Bug 1770010]: Autofill fails, when I need to unlock bitwarden.](https://bugzilla.mozilla.org/show_bug.cgi?id=1770010)

GiteaMirror commented

@novocaiin commented on GitHub (May 28, 2022):

Will this ever be resolved in Chromium?

@novocaiin commented on GitHub (May 28, 2022): Will this ever be resolved in Chromium?

GiteaMirror commented

@uOOOO commented on GitHub (Jun 1, 2022):

After upgrading Android 12, autofill doesn't work properly. In many cases, only one of password or username is filled. The device is Galaxy S20+.
e.g. https://play.google.com/store/apps/details?id=com.fineapp.yogiyo&hl=en&gl=US

@uOOOO commented on GitHub (Jun 1, 2022): After upgrading Android 12, autofill doesn't work properly. In many cases, only one of password or username is filled. The device is Galaxy S20+. e.g. https://play.google.com/store/apps/details?id=com.fineapp.yogiyo&hl=en&gl=US

GiteaMirror commented

@nilesh-akhade commented on GitHub (Jul 6, 2022):

Autofill does not work on Citi Bank Android App. androidapp://com.citiuat
https://imgur.com/a/9C9mr9Q

Copy-paste does not work either. Maybe this is because Citi App has allowed only a specific set of characters on password edit text. Like this https://stackoverflow.com/a/23212485/4417818

@nilesh-akhade commented on GitHub (Jul 6, 2022): Autofill does not work on [Citi Bank Android App](https://play.google.com/store/apps/details?id=com.citiuat). `androidapp://com.citiuat` https://imgur.com/a/9C9mr9Q Copy-paste does not work either. Maybe this is because Citi App has allowed only a specific set of characters on password edit text. Like this https://stackoverflow.com/a/23212485/4417818

GiteaMirror commented

@shalom06 commented on GitHub (Jul 20, 2022):

Ive been having the same issue with the Instagram app for android . It just auto-fill's the username and not password.

@shalom06 commented on GitHub (Jul 20, 2022): Ive been having the same issue with the Instagram app for android . It just auto-fill's the username and not password.

GiteaMirror commented

@SoyDiego commented on GitHub (Jul 29, 2022):

On mobile on the website Idea bitwarden have been written my password in USERNAME.
I tried with linked custom fields but same. The problem is ON MOBILE, in desktop works perfectly.

@SoyDiego commented on GitHub (Jul 29, 2022): On mobile on the website [Idea](https://www.idealista.com/login) bitwarden have been written my password in USERNAME. I tried with linked custom fields but same. The problem is ON MOBILE, in desktop works perfectly.

GiteaMirror commented

@digideth commented on GitHub (Aug 16, 2022):

So the issue of auto filling passwords into username fields is never going to be fixed? I've tried custom fields and still doesn't work.
Pixel 6 pro
android 12 SQ3A.220705.003.A3
chrome version 104.0.5112.69
bitwarden version version 2022.8.0

@digideth commented on GitHub (Aug 16, 2022): So the issue of auto filling passwords into username fields is never going to be fixed? I've tried custom fields and still doesn't work. Pixel 6 pro android 12 SQ3A.220705.003.A3 chrome version 104.0.5112.69 bitwarden version version 2022.8.0

GiteaMirror commented

@dbosompem commented on GitHub (Aug 16, 2022):

Hi all, apologies for the inconveniences caused. The team is keeping tabs on this issue and we'd look into these, as we keep you in the loop. Thank you for your patience.

@dbosompem commented on GitHub (Aug 16, 2022): Hi all, apologies for the inconveniences caused. The team is keeping tabs on this issue and we'd look into these, as we keep you in the loop. Thank you for your patience.

GiteaMirror commented

@shaulgo commented on GitHub (Aug 28, 2022):

Isn't there a general way to allow custom fields to work on android. If lastpass can find the field then it's technically possible. I'm a web dev. So not sure how it works in mobile. But couldn't it be possible to even allow to select by order/index of field. first field, second field...
Then if the app changes, the user can just change the order.
Not sure if this has any merit.
Anyways thanks :)

@shaulgo commented on GitHub (Aug 28, 2022): Isn't there a general way to allow custom fields to work on android. If lastpass can find the field then it's technically possible. I'm a web dev. So not sure how it works in mobile. But couldn't it be possible to even allow to select by order/index of field. first field, second field... Then if the app changes, the user can just change the order. Not sure if this has any merit. Anyways thanks :)

GiteaMirror commented

@RafailFridman commented on GitHub (Aug 29, 2022):

Autofill not working (no popup, no inline suggestion) in Binance and Bybit apps on Poco X3 NFC
Bitwarden version 2022.8.0

@RafailFridman commented on GitHub (Aug 29, 2022): Autofill not working (no popup, no inline suggestion) in Binance and Bybit apps on Poco X3 NFC Bitwarden version 2022.8.0

GiteaMirror commented

@abda11ah commented on GitHub (Aug 31, 2022):

Also Stargon Browser does not autofill as it should.
net.onecook.browser

@abda11ah commented on GitHub (Aug 31, 2022): Also Stargon Browser does not autofill as it should. net.onecook.browser

GiteaMirror commented

@digideth commented on GitHub (Sep 1, 2022):

espn.com doesn't work at all. No logins are even offered in chrome. Can't even test Autofill. Uri is set to espn.com so it is completely broken.

@digideth commented on GitHub (Sep 1, 2022): espn.com doesn't work at all. No logins are even offered in chrome. Can't even test Autofill. Uri is set to espn.com so it is completely broken.

GiteaMirror commented

@smtgpm commented on GitHub (Sep 24, 2022):

Hi
For me auto fill also has been getting worse. Latest issue, the service itself keeps turning off (I do not have battery optimization for BW). And even when the service is on, it never proposes auto fill anymore on any site, I first have to manually open BW, connect, go back to the site and then it'll suggest (sometimes) autofilling. Paypal.com never works though

@smtgpm commented on GitHub (Sep 24, 2022): Hi For me auto fill also has been getting worse. Latest issue, the service itself keeps turning off (I do not have battery optimization for BW). And even when the service is on, it never proposes auto fill anymore on any site, I first have to manually open BW, connect, go back to the site and then it'll suggest (sometimes) autofilling. Paypal.com never works though

GiteaMirror commented

@supermansaga commented on GitHub (Oct 18, 2022):

The following apps 1) NYTimes; 2) Washington Post; 3) WSJ on Android 13 of Google's Pixel 7 Pro don't seem to have auto fill for username well, despite I believe I have enabled them. Many thanks. NYTimes suck at filling out password too.

@supermansaga commented on GitHub (Oct 18, 2022): The following apps 1) NYTimes; 2) Washington Post; 3) WSJ on Android 13 of Google's Pixel 7 Pro don't seem to have auto fill for username well, despite I believe I have enabled them. Many thanks. NYTimes suck at filling out password too.

GiteaMirror commented

@swamp2 commented on GitHub (Oct 28, 2022):

Etrade App on Android 13 does not support Autofill nor provide an option to memorize the login info.

@swamp2 commented on GitHub (Oct 28, 2022): Etrade App on Android 13 does not support Autofill nor provide an option to memorize the login info.

GiteaMirror commented

@kuxv commented on GitHub (Nov 10, 2022):

"Můj vlak" app does not support filling in credit card details on Lineage OS 19. It does not offer option to autofill(all 4 autofill options turned on as well as unrestricted battery usage). I've also tried it with pCloud Pass and that offers the option to fill in the credit card info.

@kuxv commented on GitHub (Nov 10, 2022): "Můj vlak" app does not support filling in credit card details on Lineage OS 19. It does not offer option to autofill(all 4 autofill options turned on as well as unrestricted battery usage). I've also tried it with pCloud Pass and that offers the option to fill in the credit card info.

GiteaMirror commented

@digideth commented on GitHub (Dec 31, 2022):

Half broken on login.aol.com won't recognize the user name field is on the page. If you know your username and get to the next page it will fill the password.

@digideth commented on GitHub (Dec 31, 2022): Half broken on login.aol.com won't recognize the user name field is on the page. If you know your username and get to the next page it will fill the password.

GiteaMirror commented

@kurczynski commented on GitHub (Jan 4, 2023):

Half broken on login.aol.com won't recognize the user name field is on the page. If you know your username and get to the next page it will fill the password.

FWIW this also happens when trying to log in to redhat.com on both mobile and desktop.

@kurczynski commented on GitHub (Jan 4, 2023): > Half broken on login.aol.com won't recognize the user name field is on the page. If you know your username and get to the next page it will fill the password. FWIW this also happens when trying to log in to [redhat.com](https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/auth?response_type=code&client_id=https%3A%2F%2Fwww.redhat.com%2Fwapps%2Fugc-oidc&redirect_uri=https%3A%2F%2Fwww.redhat.com%2Fwapps%2Fugc%2Fsso%2Flogin&state=41fa133d-3a3e-4d16-859e-f3cf0266b5ab&login=true&scope=openid) on both mobile and desktop.

GiteaMirror commented

@larena1 commented on GitHub (Jan 4, 2023):

@digideth @kurczynski could you verify if you experience the same issue also with other popular password management apps or if it works correctly? If the latter, there might be a chance for this to be fixed if Bitwarden maintainers look into it.

@larena1 commented on GitHub (Jan 4, 2023): @digideth @kurczynski could you verify if you experience the same issue also with other popular password management apps or if it works correctly? If the latter, there might be a chance for this to be fixed if Bitwarden maintainers look into it.

GiteaMirror commented

@kurczynski commented on GitHub (Jan 4, 2023):

@larena1 I don't have any other password management apps, but I assume this is caused by Bitwarden not recognizing the field as a login because there is no password field displayed yet. Not sure if the password field isn't generated until a username is given or if it's just labeled differently in the DOM.

@kurczynski commented on GitHub (Jan 4, 2023): @larena1 I don't have any other password management apps, but I assume this is caused by Bitwarden not recognizing the field as a login because there is no password field displayed yet. Not sure if the password field isn't generated until a username is given or if it's just labeled differently in the DOM.

GiteaMirror commented

@digideth commented on GitHub (Jan 4, 2023):

@larena1 It should not matter if this happens on the password apps! Bitwarden is broken and they should fix their app

@digideth commented on GitHub (Jan 4, 2023): @larena1 It should not matter if this happens on the password apps! Bitwarden is broken and they should fix their app

GiteaMirror commented

@larena1 commented on GitHub (Jan 4, 2023):

@digideth I agree with you, but, as you can see, despite countless complaints and reports over the years, nobody from Bitwarden is looking into it. Their focus seems to be on enterprise features rather than on proper core functionality and UX.

@eliykat Are there any results yet from you actively looking into fixing autofill issues on Android or mobile in general for almost two years? It seems nothing has changed so far and compared to other commercial password managers like LastPass, Enpass or 1Password, Bitwarden still has one of the poorest autofill implementations.

Isn't there anybody on your team who knows the autofill API well enough to fix the current implementation at least to a point that it is comparable to other password managers?

@larena1 commented on GitHub (Jan 4, 2023): @digideth I agree with you, but, as you can see, despite countless complaints and reports over the years, nobody from Bitwarden is looking into it. Their focus seems to be on enterprise features rather than on proper core functionality and UX. @eliykat Are there any results yet from you actively looking into fixing autofill issues on Android or mobile in general for almost two years? It seems nothing has changed so far and compared to other commercial password managers like LastPass, Enpass or 1Password, Bitwarden still has one of the poorest autofill implementations. Isn't there anybody on your team who knows the autofill API well enough to fix the current implementation at least to a point that it is comparable to other password managers?

GiteaMirror commented

@eliykat commented on GitHub (Jan 4, 2023):

Hi @larena1, I created the issue but I'm not a mobile dev, so I'm not much help here. I've raised your question internally to see if anyone can provide an update.

@eliykat commented on GitHub (Jan 4, 2023): Hi @larena1, I created the issue but I'm not a mobile dev, so I'm not much help here. I've raised your question internally to see if anyone can provide an update.

GiteaMirror commented

@digideth commented on GitHub (Jan 5, 2023):

@eliykat thank you!

I've given up and started to test others again and tbh chrome is leading the pack as far as working correctly all the time for websites...

@digideth commented on GitHub (Jan 5, 2023): @eliykat thank you! I've given up and started to test others again and tbh chrome is leading the pack as far as working correctly all the time for websites...

GiteaMirror commented

@streetwolf commented on GitHub (Jan 5, 2023):

Just about every site doesn't autofill for me. One thing I didn't notice before is that on one site when I bring up the KB to enter my userid one of the KB suggestions is the BW entry for the site. This URL listed is the app I use to get to the site not through a web browser. Clicking on that fills in the userid/pw. I've only seen this on one site so far.

@streetwolf commented on GitHub (Jan 5, 2023): Just about every site doesn't autofill for me. One thing I didn't notice before is that on one site when I bring up the KB to enter my userid one of the KB suggestions is the BW entry for the site. This URL listed is the app I use to get to the site not through a web browser. Clicking on that fills in the userid/pw. I've only seen this on one site so far.

GiteaMirror commented

@xyxzxyz commented on GitHub (Jan 20, 2023):

@streetwolf same here, unfortunately. Now even on Microsoft login page, autofill doesn't work properly anymore. It filled password into username field and has been behaving like this more commonly.

@xyxzxyz commented on GitHub (Jan 20, 2023): @streetwolf same here, unfortunately. Now even on Microsoft login page, autofill doesn't work properly anymore. It filled password into username field and has been behaving like this more commonly.

GiteaMirror commented

@johnebs commented on GitHub (Jan 21, 2023):

Recently switched to Bitwarden and just came up with this issue I consider it to be unacceptable that 9 months after the initial (known) report, the issue is still present. Having the password manager auto populate the password into none password fields is a security risk. Bitwarden sould NOT populate the password if its not confident that the field is a password field.

My dad uses Outlook.com and I was surprised to see Bitwarden freely populating the password in plain text into the email field. This field get cached and now his keyboard has it stored as a valid auto complete text. Huge security risk. This needs to get fixed ASAP. My confidence in the product has gone way down. 9 month... unacceptable, specially for such an easy fix.

If FIELDID <> password then Populate email o Nothing...

@johnebs commented on GitHub (Jan 21, 2023): Recently switched to Bitwarden and just came up with this issue I consider it to be unacceptable that 9 months after the initial (known) report, the issue is still present. Having the password manager auto populate the password into none password fields is a security risk. Bitwarden sould NOT populate the password if its not confident that the field is a password field. My dad uses Outlook.com and I was surprised to see Bitwarden freely populating the password in plain text into the email field. This field get cached and now his keyboard has it stored as a valid auto complete text. Huge security risk. This needs to get fixed ASAP. My confidence in the product has gone way down. 9 month... unacceptable, specially for such an easy fix. If FIELDID <> password then Populate email o Nothing...

GiteaMirror commented

https://github.com/bitwarden/mobile/issues/640

@larena1 commented on GitHub (Jan 21, 2023):

9 months? This was reported more than 3 years ago. Truth is nobody from Bitwarden cares at all or they just lack the skills required for a proper autofill implementation that is on par with competitors.

@larena1 commented on GitHub (Jan 21, 2023): 9 months? This was reported more than 3 years ago. Truth is nobody from Bitwarden cares at all or they just lack the skills required for a proper autofill implementation that is on par with competitors. https://github.com/bitwarden/mobile/issues/640

GiteaMirror commented

@johnebs commented on GitHub (Jan 21, 2023):

Well... I stand corrected and it's way worse that I thought then...

@johnebs commented on GitHub (Jan 21, 2023): > Well... I stand corrected and it's way worse that I thought then...

GiteaMirror commented

@THEOCKID commented on GitHub (Jan 21, 2023):

Ok everyone here's the real problem.

Go try the competitors. Or just take my word for it as I've tried 1password, keypass, LastPass, Keeper, etc. And I found them all lacking compared to bitwarden when it comes to flexibility in password entry.

For instance, I'll go to a website and unless the URL in the pw manager matches exactly, you're Fd. Won't fill anything. With bitwarden you always have the option to pick a near match. And it's way more flexible for multiple matches. Example Gmail. I've got 20 or more emails and it's relatively easy to pick from a list of them in BW, not so in others.

I know their auto fill has always been problematic. But try the others and see how it goes. I'm sorry, I know the others UX is better looking etc and BW hasn't really changed in years. But I'm a function over form kinda guy, and I'll jump ship when the others do as good.

@THEOCKID commented on GitHub (Jan 21, 2023): Ok everyone here's the real problem. Go try the competitors. Or just take my word for it as I've tried 1password, keypass, LastPass, Keeper, etc. And I found them all lacking compared to bitwarden when it comes to flexibility in password entry. For instance, I'll go to a website and unless the URL in the pw manager matches exactly, you're Fd. Won't fill anything. With bitwarden you always have the option to pick a near match. And it's way more flexible for multiple matches. Example Gmail. I've got 20 or more emails and it's relatively easy to pick from a list of them in BW, not so in others. I know their auto fill has always been problematic. But try the others and see how it goes. I'm sorry, I know the others UX is better looking etc and BW hasn't really changed in years. But I'm a function over form kinda guy, and I'll jump ship when the others do as good.

GiteaMirror commented

@ghost commented on GitHub (Jan 21, 2023):

I’ve been on Android most of my life, but there seems to be major bugs with the Android autofill API (with 3rd party password managers) that Google ignores. I believe there are numerous bug reports that have been unresolved for years.

I left Android for Apple last year and I no longer have any issues. I still miss Android but there were so many little bugs and annoyances that no longer exist after switching to Apple.

It’s a shit situation all around and it sucks that the Bitwarden team just ignores the problem and everyone here.

Nobody should have to abandon Android for a stable experience, but here we are. 😩

@ghost commented on GitHub (Jan 21, 2023): I’ve been on Android most of my life, but there seems to be major bugs with the Android autofill API (with 3rd party password managers) that Google ignores. I believe there are numerous bug reports that have been unresolved for years. I left Android for Apple last year and I no longer have any issues. I still miss Android but there were so many little bugs and annoyances that no longer exist after switching to Apple. It’s a shit situation all around and it sucks that the Bitwarden team just ignores the problem and everyone here. Nobody should have to abandon Android for a stable experience, but here we are. 😩

GiteaMirror commented

@johnebs commented on GitHub (Jan 21, 2023):

As a matter of fact I decided to star using Bitwarden because it appeared to be very secure and I'm very pro FLOSS software (even though I'm a paying Bitwarden customer). I've been a LastPass user for years, then tried 1Password for a few months and KeePass for a few days. While the AutoFill has always been problematic (as in not alway working), none of them had the issue of placing the password in any field other than the Password field.

This is an issue exclusive to Bitwarden (to my knowledge). The issues should not be categorized as an inconvenience since it's also a security issue. You can assume that any field other than the password field is not secure. Placing the password on any non password field opens the password to snooping, caching/loging. Nobody should be 'fine' with that bug still active after so many years.

@johnebs commented on GitHub (Jan 21, 2023): > As a matter of fact I decided to star using Bitwarden because it appeared to be very secure and I'm very pro FLOSS software (even though I'm a paying Bitwarden customer). I've been a LastPass user for years, then tried 1Password for a few months and KeePass for a few days. While the AutoFill has always been problematic (as in not alway working), none of them had the issue of placing the password in any field other than the Password field. This is an issue exclusive to Bitwarden (to my knowledge). The issues should not be categorized as an inconvenience since it's also a security issue. You can assume that any field other than the password field is not secure. Placing the password on any non password field opens the password to snooping, caching/loging. Nobody should be 'fine' with that bug still active after so many years.

GiteaMirror commented

https://developer.android.com/reference/android/text/InputType

@larena1 commented on GitHub (Jan 21, 2023):

I looked into this now.

On https://www.paypal.com/signin Bitwarden will falsely detect the email field as a password field because it has TYPE_TEXT_VARIATION_PASSWORD. The field also has TYPE_TEXT_VARIATION_WEB_EMAIL_ADDRESS, so it obviously is not a password field.

Also according to the official documentation, password fields should be tested against TYPE_CLASS_TEXT | TYPE_TEXT_VARIATION_VISIBLE_PASSWORD.

The issue can definitely be fixed and it's absolutely devastating that nobody from team Bitwarden ever cared to look into this further in more than 3 years.

@larena1 commented on GitHub (Jan 21, 2023): I looked into this now. On https://www.paypal.com/signin Bitwarden will falsely detect the email field as a password field because it has TYPE_TEXT_VARIATION_PASSWORD. The field also has TYPE_TEXT_VARIATION_WEB_EMAIL_ADDRESS, so it obviously is not a password field. Also according to the official documentation, password fields should be tested against TYPE_CLASS_TEXT | TYPE_TEXT_VARIATION_VISIBLE_PASSWORD. https://developer.android.com/reference/android/text/InputType The issue can definitely be fixed and it's absolutely devastating that nobody from team Bitwarden ever cared to look into this further in more than 3 years.

GiteaMirror commented

https://github.com/bitwarden/mobile/issues/2315
https://github.com/bitwarden/mobile/issues/2316
https://github.com/bitwarden/mobile/issues/2318
https://github.com/bitwarden/mobile/issues/2319

@SergeantConfused commented on GitHub (Jan 21, 2023):

We apologize for any confusion we may have caused regarding the tracking mechanism we were using for reporting Autofill issues on Mobile. We were relying on a form submission we track separately as mentioned in the original post. We have created a few new specific GitHub issues for sites recently reported and we will track these individually in GitHub until we determine the best way for Autofill issues to be reported going forward. We appreciate your understanding and we will work with the Engineering team to get these issues resolved.

@SergeantConfused commented on GitHub (Jan 21, 2023): We apologize for any confusion we may have caused regarding the tracking mechanism we were using for reporting Autofill issues on Mobile. We were relying on a form submission we track separately as mentioned in the original post. We have created a few new specific GitHub issues for sites recently reported and we will track these individually in GitHub until we determine the best way for Autofill issues to be reported going forward. We appreciate your understanding and we will work with the Engineering team to get these issues resolved. https://github.com/bitwarden/mobile/issues/2315 https://github.com/bitwarden/mobile/issues/2316 https://github.com/bitwarden/mobile/issues/2318 https://github.com/bitwarden/mobile/issues/2319

GiteaMirror commented

@larena1 commented on GitHub (Jan 22, 2023):

@SergeantConfused could you also track https://github.com/tutao/tutanota/issues/4499 separately as another Bitwarden specific autofill issue?

@larena1 commented on GitHub (Jan 22, 2023): @SergeantConfused could you also track https://github.com/tutao/tutanota/issues/4499 separately as another Bitwarden specific autofill issue?

GiteaMirror commented