Autofill isn't working on mobile (generally or for a specific site or app) #1389
Comments
eliykat
changed the title
|
@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. |
|
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? |
|
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. |
|
As the Auto-Fill 'feature' has never, ever worked at all for me on any of my devices, I just don't use it. In fact, this is not a Bitwarden problem. 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. |
|
Is there any time frame to improve the Auto-Fill behavior following the inputs provided in the google doc file? |
|
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. |
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. |
|
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.
Yeah, okay bud. 👍 |
|
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. |
|
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. |
|
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. |
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) |
|
Hi, KepassDX password manager has no issue with autofill in my Android 10 except that it does not copy OTP. Thanks |
|
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!!! |
|
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. |
|
Yeah, I was hoping to see some improvements in this area. Can anyone on the Bitwarden team provide an update? |
This seems to be a very complex bug, that involves not only the password manager but also the browsers and maybe even the keyboards. |
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. |
|
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 phoneGo to Auto-fill Services, and turn off everything: 1st Use Inline Autofill, then Auto-fill Service. Then Use Draw-Over, then Use AccessibilityQuit BWClose all appsRestart phoneUpon 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. |
|
@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 |
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. |
|
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-maui/issues/1509 that could be fixed easily... If anybody was working on it but that's not the case and it's a pity |
|
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. |
|
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 What are you using instead? I'm planning to do the same. |
|
@olfek I am trying a few and have not decided yet. |
|
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. |
|
Hi |
|
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. |
|
Etrade App on Android 13 does not support Autofill nor provide an option to memorize the login info. |
|
"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. |
|
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. |
|
@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 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. |
|
@larena1 It should not matter if this happens on the password apps! Bitwarden is broken and they should fix their app |
|
@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? |
|
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 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... |
|
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 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. |
|
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... |
|
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. |
|
Well... I stand corrected and it's way worse that I thought then... |
|
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. |
|
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. 😩 |
|
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. |
|
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. |
|
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-maui/issues/2315 |
|
@SergeantConfused could you also track tutao/tutanota#4499 separately as another Bitwarden specific autofill issue? |
Sure thing (#2323). |
Describe the Bug
We are aware of some situations where the Bitwarden mobile app will not autofill information correctly. This may be due to:
This includes situations where:
This is something the Bitwarden team is actively working on but need your help as a community and active Bitwarden users!
Note: this issue is for the Bitwarden mobile app only. If you're having issues with the browser extension on a computer, please go to this issue instead.
Expected Result
If you have autofill enabled (following the instructions for Android or iOS, and you click a field in a login form in your mobile browser or an app, you should have the option to autofill the credentials from your Bitwarden vault.
Actual Result
This works most of the time, but not always and it can depend on many, many factors. Some sites, apps or devices simply don't work, some don't work consistently and others who knows. This is what we're aiming to fix!
Call to Action
Below is a link to a Google Form that we have created for capturing information that will help us track down all of these pages, apps, devices and/or OS versions where Bitwarden has failed to autofill your information. You may submit as many as you like, just please help us help you and the community by providing meaningful information and only those sites/pages where it legitimately doesn't work.
Report autofill failure - mobile
If you've been sent to this issue because another issue you had open was closed as a duplicate, thank you for taking the time to submit the issue to us, however we truly need to track this under a single item in aggregate fashion so we can manage it holistically and ensure we're taking broad measures that will improve this behavior with the maximum benefit to all. Please consider using the linked form above to submit the prior sites you had reported in the issue closed.
The text was updated successfully, but these errors were encountered: