Autofill not working on Chrome Android

[6w6OoPIRf3et9qT8tv7EyO1N5Y6RBqVD0zdY9ih]

Autofill is not consistent and not working on chrome Android

[noWz78I9OeZZqWbCMBrDseFbCT7YSMpzbul5Uyh]

Same experience here, accessibility services with bitwarden are not offered if Our device is in "please do not disturb mode"

[X7gDIkFzoLkK2a23WY5mDsJYAJFWZVE8SepD7WV]

I find the autofill service works better if you select one of the input fields prior to attempting to autofill. I have only been using Bitwarden for a couple days though, but that is my experience thus far. This is when filling fields in Chrome using accessibility service, using the beta android app.

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

Need more information, such as which autofill service you are using here.

[QfxgiEECqEYhL75PpTwHKHWjdLs1Fl3VZ8cjCwi]

I'm having the same problem on the Android Q Beta on a Pixel 3. I'm using the Andoid Autofill Framework, though I tried enabling the Accessibility Autofill and that did not correct the problem.

[6w6OoPIRf3et9qT8tv7EyO1N5Y6RBqVD0zdY9ih]

Need more information, such as which autofill service you are using here.

I am using the latest Android version of the app on Android P. Sometimes it works and sometimes not. It's inconsistent. I had quit the chrome app multiple to get it working.

[X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI]

It might be helpful to disable adaptive battery for Bitwarden in Android Pie. If your device has any form of battery optimization baked in, sometimes it helps to disable it for certain applications that you want to always receive notifications / prompts for.

[6w6OoPIRf3et9qT8tv7EyO1N5Y6RBqVD0zdY9ih]

Same experience here, accessibility services with bitwarden are not offered if Our device is in "please do not disturb mode"

Turning off DND mode solved my issue. Is there a workaround for this? Because my DND is scheduled and I don't want to turn off.

[UEBqheEXswNNy6eAqlWCfgz0tGrd00waj4taxzV]

It's not working anymore for me too using Kiwi browser beta (and bitwarden beta). it's been 1 week now it's stopped. I tried all you said, but no...

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

I'm having the same issue, too, although it was working for a while. I was hoping it was a configuration or system issue, because it only stopped working a couple days ago. Here's what I gathered so far.

Expected Behavior

The Bitwarden AutoFill Service should offer a drop in the "username" or "password" field.

Current Behavior

• There is no dropdown.
• Selecting either field does not cause the dropdown to appear.

Current Configuration

• Android 8.0.0
• OxygenOS 5.0.8
• "Auto Fill Service" enabled
• "Auto Fill Accessibility Service" disabled

Troubleshooting Steps

• Change lock timeout to various values
• Enabled / Disabled "Auto Fill Accessibility Service"
• Force stopped app
• Cleared cache
• Deleted all internal storage
• Uninstall/Reinstall app
• Disable doze mode

<-- Chrome -->

• Cleared all history
• Disabled safe browsing
• Disabled page predictions
• Allowed pop ups and redirects
• Force stop and clear cache through system
• Disable/Enable Chrome

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

@kspearrin It's worth mentioning, too, that the autofill service works in some other apps, but not others.

<-- Does not work -->

• Chrome
• ProtonMail
• Shipt (Meijer)
• Wall Street Journal

<-- Does work -->

• Workday
• Robinood
• Sync.com
• FastHub

I'm thinking that the recent privacy and security improvements that Google made may be interfering with BitWarden, but I'm not sure on the other apps.

I hope this helps my friend. Good app. Just bought the family plan.

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

I tested this on other password management apps, such as 1Password, and they do not seem to be working either. Seems that Chrome broke something.

[wps2OROaTFpBTdhrYYAivJLQMO0PbqMQCdq3la2]

I have also tested autofill with Keepass2Android and Enpass - both work in Firefox but do not in Chrome (stable and beta). (Nexus 5X on PixelExperience, Android 9)

[X0agGbCofOzSNzmOeMNIArh3G3KDQrMX4f5BdFT]

FWIW, same here: Bitwarden & Firefox are OK. On Chrome, no.

[UEBqheEXswNNy6eAqlWCfgz0tGrd00waj4taxzV]

Hm, well it's unconsistent with firefox. When the pop up is showing (not always), it's not like it should be. It's really strange.

[hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX]

Just chiming in that I'm having the same issue. I've been emailing back and forth with support over the weekend but have not yet found a solution.

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

@nemchik :sweat_smile: I don't think you'll find much better support than what you got here

[UEBqheEXswNNy6eAqlWCfgz0tGrd00waj4taxzV]

Actually, we just need to know if someone is still working on the app or is it abandoned? I just move everything in bitwarden, no luck for me, and tell my family to do the same... we need to know if it's still supported. Or forked?

[hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX]

Well it does look like a new release (1.22.1) was pushed that lists a fix for this issue, so in the very least it's being looked at. I haven't seen the update come across the Google play store yet.

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

@fruity101079 I meant that the guy who wrote the thing is participating in this thread.

[hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX]

https://github.com/bitwarden/mobile/releases/tag/v1.22.1

[UEBqheEXswNNy6eAqlWCfgz0tGrd00waj4taxzV]

I just see anew release has been pushed. great news. Thanks the dev :)

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

This issue is still outstanding. We are not receiving autofill event from Chrome anymore. I am not sure if this is an OS bug or a Chrome app bug, but from what I can tell with my testing, no password manager apps are working with Chrome (and some other apps) now.

[UEBqheEXswNNy6eAqlWCfgz0tGrd00waj4taxzV]

Just for info, I just notice that the accessibility service was disabled, again... And of course now it's working again with firefox and kiwi (so chrome also I guess).

[RHGs7N0wdzJsUgbqpSn4btVjAyY3CXQRtk4ZMGg]

Works fine for me in stock chrome, but still having an issue where the inline filler doesn't work in Kiwi - only the drop down auto-fill service. Is this the only one available for Kiwi?

[MuOWBWbRYss2VJUZxNmti8bRTypOBuXLmjyvNC3]

I seem to have the same symptoms, where Pie autofill does not work consistently in Chrome. I have a OnePlus 6T with Android 9 and OxygenOs 9.0.14.

A workaround for me is to:

• show all apps and kill Chrome
• reopen Chrome (thankfully the tabs are restored even after killing)
• autofill is properly detected

Bitwarden is in the "Don't optimize" Battery optimization list.

I have Bitwarden 1.22.0, but apparently 1.22.1 released 2 weeks ago is not yet available in the Play store for me.

[X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI]

The latest Beta has been working great for me. I was starting to have a ton of these issues with the old version as well. @gotson Have you tried opting into the Beta?

[MuOWBWbRYss2VJUZxNmti8bRTypOBuXLmjyvNC3]

The latest Beta has been working great for me. I was starting to have a ton of these issues with the old version as well. @gotson Have you tried opting into the Beta?

i was about to try that indeed! Will report whether it works or not on my issue.

[X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI]

I spoke too soon, I guess I had the accessibility service enabled. The auto-fill framework is still not working for me. Overall though, the beta feels much better assuming you're using the accessibility service. I'm not having any more long hangs when opening the vault and stuff. I don't know, the old version was starting to feel really buggy and the beta just feels overall a lot better.

[hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX]

I've been using the 2.0 beta since shortly before the 2.0 stable release tagged here in the repo and it's been about 50/50 on the popunder, which is better than 0 on the 1.x version.

[MuOWBWbRYss2VJUZxNmti8bRTypOBuXLmjyvNC3]

I still have the problem with the 2.0.3 installed from the PlayStore beta :(

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

I had to lock and factory reset my phone to update to Android Pie. After updating OxygenOS and Chrome, it's working.

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

I started having problems again after running more updates. I disabled Chrome's "Addresses and More" option, and BitWarden started working flawlessly again.

[Cr7TfVDZJtQhfIqIkfuCsYCDqj4XG6E0UCllniq]

I still have a lot of issues with autofill in Chrome, which is resolved by killing Chrome and then opening it again. Would be nice to find a solution to this problem..

[goVN1FleDxx1Ww8ghKOP3fTx8cQ4n0FGKUCJxd7]

@JonathonAnderson Disabling "addresses and more" also fixed it for me in chrome. Thanks a lot, I've been fighting with bitwarden for a couple months to get this since I switched from lastpass (which worked fine on android...)

[5eaFDvL0t2re4CFQWQWwoiSVcZEtJMUDjhtRuPq]

@JonathonAnderson: Thanks, that solved it for me as well, both in Chrome and in Lynket!

I also discovered that " Save and fill payment methods" under "Payment methods" needs to be enabled for me in order for Bitwarden to work properly. Weird.

[X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI]

@kspearrin, Is it recommended to use an alternate browser such as Firefox on mobile from now on then? It seems like Google keeps breaking things / making controversial changes in Chrome a lot lately.

Is there anything we can do to get Google to stop making breaking changes to Chrome, especially in regards to password managers?

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

Firefox seems to work well with autofill, which seems odd since Chrome is also a Google product, you would think it would work the best. I'd recommend another browser if autofill is important to you.

[O5lyQ1exQuh3MTcqHllqpluXhp7k8mEHPFUEEzD]

I'd recommend another browser if autofill is important to you.

Or privacy

[TTiQsP5XjnV7swCm7qfhygLCIkcG90kcP07zYz3]

As I mentioned in #562 I'm getting this issue as well but LastPass still has no problem filling the Chrome login form.. https://developer.android.com/guide/topics/text/autofill ??

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

That's because you are using the LastPass accessibility service. Bitwarden's accessibility service works fine as well.

[TTiQsP5XjnV7swCm7qfhygLCIkcG90kcP07zYz3]

No, I turned off all LP.. turned on all BW.. still not finding the URL from Chrome. My point was that LastPass is getting the URL from Chrome when Bitwarden is not (in relation to your comment that other password fillers are also affected and Chrome is the issue.. but why is LP still working?)

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

@ghhv LastPass's standard autofill service will also has this issue. Their accessibility service works just like Bitwarden's.

[TTiQsP5XjnV7swCm7qfhygLCIkcG90kcP07zYz3]

@kspearrin Hmm. but it doesn't have the issue. I'll send you some screen shots tomorrow to help work out what is happening..

[G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF]

@kspearrin I added credentials for a site of mine to LastPass and switched my autofill service to LastPass. As you can see in the screenshot below, it works with LastPass.

When I switch to Bitwarden, however, I only get a "Go to my vault" popup. When pressed, the displayed shows the domain as "com.google.chrome" instead of the URL of the site I am trying to autofill on. This issue used to occur only sporadically, but it has lately been happening consistently.

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

@hmnd That appears to be the LastPass accessibility service, not the autofill service. Can you confirm?

[hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX]

I can confirm this as well. com.google.chrome is a common issue for me. I can sometimes return to the site and tap the notification again and it'll work correctly, but at times it takes multiple tries.

The LastPass window in the screenshot above draws over the screen which is what I thought Google was placing restrictions on recently, but it always worked for me. An issue I had with the LastPass draw over was it opened a lot more frequently than I needed it to.

[G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF]

@kspearrin Yup, that's correct. This seems like a Chrome issue, so could it maybe be possible to disable Bitwarden autofill in favour of the accessibility service for Chrome?

[X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI]

I had to switch Browsers. Actually switched entirely to iOS and now Bitwarden works flawlessly.

Chrome is seriously buggy as all hell with Bitwarden. I do not recommend it.

[pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P]

@hmnd Yes, as I previously mentioned, Chrome is bugged which is why neither Bitwarden or LastPass work with it when using the autofill service. You will need to use the accessibility service until Google fixes the problem.

[G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF]

@kspearrin I see. I also just tried autofill on Firefox Preview and it looks like Firefox only gives BW the root domain (ie. without subdomain or path)? Do you know if that's a Firefox issue?