Autofill not working on Chrome Android

[pavankjadda]

Autofill is not consistent and not working on chrome Android

[m3gg3]

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

[ouldsmobile]

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.

[kspearrin]

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

[death2cupbots]

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.

[pavankjadda]

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.

[douglasparker]

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.

[pavankjadda]

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.

[fruity101079]

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...

[JonathonAnderson]

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

[JonathonAnderson]

@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.

[kspearrin]

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.

[finderAUT]

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)

[niconikoC]

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

[fruity101079]

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.

[nemchik]

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.

[JonathonAnderson]

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

[fruity101079]

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?

[nemchik]

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.

[JonathonAnderson]

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

[nemchik]

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

[fruity101079]

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

[kspearrin]

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.

[fruity101079]

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).

[Avrution]

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?

[gotson]

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.

[douglasparker]

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?

[gotson]

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.

[douglasparker]

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.

[nemchik]

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.

[gcvl]

Since Android 7.0, Android uses file-based rather than full-disk encryption, which allows accessibility services to run at boot without affecting the level of encryption of user files.

I'm not convinced. On my Android 9 device, when trying to enable the Bitwarden Accessibility Service, I'm greeted with this warning:

If you turn on Bitwarden, your device won't use your screen lock to enhance data encryption.

If my personal locking mechanism isn't used, then what is, some default encryption key? Doesn't sound that secure to me. Obviously I haven't enabled the Accessibility Service not even once because of this warning message.

Just turn on Bitwarden and then set up the PIN again and enable "Secure Startup" when asked. At this point, you should be fine with both the accessibility service and encryption (tried with other devices still featuring full disk encryption).

[Perkolator]

Since Android 7.0, Android uses file-based rather than full-disk encryption, which allows accessibility services to run at boot without affecting the level of encryption of user files.

I'm not convinced. On my Android 9 device, when trying to enable the Bitwarden Accessibility Service, I'm greeted with this warning:

If you turn on Bitwarden, your device won't use your screen lock to enhance data encryption.

If my personal locking mechanism isn't used, then what is, some default encryption key? Doesn't sound that secure to me. Obviously I haven't enabled the Accessibility Service not even once because of this warning message.

Just turn on Bitwarden and then set up the PIN again and enable "Secure Startup" when asked. At this point, you should be fine with both the accessibility service and encryption (tried with other devices still featuring full disk encryption).

Hmm, I thought that it was already established that my device has file-based encryption, not full-disk encryption as in your tests, and that there's at least a theoretically proven exploit for my device if I enable any accessibility services.

[johns2s]

Unfortunately, this is also a problem even with the new autofill API in Android 11. I thought I found a pattern of working twice before needing a relaunch of Chrome, but upon further testing it seems to still be basically random.

[fmeum]

Unfortunately, this is also a problem even with the new autofill API in Android 11. I thought I found a pattern of working twice before needing a relaunch of Chrome, but upon further testing it seems to still be basically random.

I have submitted patches to both Chromium and the Android Open Source Project that should resolve this issue. I will post an update here once Chrome Canary includes the patch.

[andreaippo]

Unfortunately, this is also a problem even with the new autofill API in Android 11. I thought I found a pattern of working twice before needing a relaunch of Chrome, but upon further testing it seems to still be basically random.

I have submitted patches to both Chromium and the Android Open Source Project that should resolve this issue. I will post an update here once Chrome Canary includes the patch.

Fabian, I'm super eager to test your patch. If it works Imma ask you for your paypal info since I would gladly offer you a beer.
That's kind of sad tho to see how Google is giving less and less importance to issues that don't affect its own services.
To my knowledge, as long as you stick with Chrome and Google's password "manager", you are fine since you are inside their walled garden (hold on, that reminds me something!).
I refuse to use Google's password "manager" since it's not an actual manager and lacks all the cross-platform capabilities of a dedicated app/service like BW, Keepass, you name it...

[johns2s]

@FabianHenneke while Canary works longer with your patch, after a while it reverts to the same behavior we've been seeing. Will I need to wait for the AOSP patch to land?

[fmeum]

@FabianHenneke while Canary works longer with your patch, after a while it reverts to the same behavior we've been seeing. Will I need to wait for the AOSP patch to land?

@johns2s I have another Chromium patch lined up: https://chromium-review.googlesource.com/c/chromium/src/+/2546900

The previous issue shadowed this additional bug that causes Autofill to stop working after the fill UI has been shown ten times. With that patch Autofill should work reliably unless you have ten forms on a single page and never switch tabs.

[fmeum]

@johns2s @andreaippo Please try Chrome 89.0.4342.0, which is the current Canary release. It should offer reliable Autofill.

Quite possibly support for saving password will also land in Chrome 89.

[simonkotwicz]

@fmeum I tried the current canary release and noticed a different issue that isn't in the stable release. If your vault is locked and you have to unlock the vault first and select a password, it doesn't fill in that password. You have to then tap on the password again in the inline autofill to actually fill in the password.

[johns2s]

@fmeum I tried the current canary release and noticed a different issue that isn't in the stable release. If your vault is locked and you have to unlock the vault first and select a password, it doesn't fill in that password. You have to then tap on the password again in the inline autofill to actually fill in the password.

Also experiencing this, though looks like the main issue is fixed!

[fmeum]

@fmeum I tried the current canary release and noticed a different issue that isn't in the stable release. If your vault is locked and you have to unlock the vault first and select a password, it doesn't fill in that password. You have to then tap on the password again in the inline autofill to actually fill in the password.

Thanks for the report, I submitted another CL to get this fixed. It didn't show up with the password managers I tested with, so thanks for making me aware of it!

[quthla]

@fmeum

https://bugs.chromium.org/p/chromium/issues/detail?id=1014945

Is this still an issue with latest canary version? Is your password manager also affected?

[fmeum]

This is still an issue and does not depend on the particular kind of password manager you are using. I don't think I'm in a position to improve the situation as Chrome's accessibility backend is quite complex.

[fmeum]

@fmeum I tried the current canary release and noticed a different issue that isn't in the stable release. If your vault is locked and you have to unlock the vault first and select a password, it doesn't fill in that password. You have to then tap on the password again in the inline autofill to actually fill in the password.

@johns2s @simonkotwicz This is fixed for me in 89.0.4347.0, please give it a try.

If you find any other Autofill issue that is not also present with Accessibility, please let me know.

[simonkotwicz]

thanks, it's fixed for me as well in 89.0.4347.0

[johns2s]

Works for me too! Thanks for your work on this.

[fmeum]

@andreaippo You might also want to take a look.

I have a lead regarding the Accessibility issue now, I will see whether I can do something about it.

[andreaippo]

@andreaippo You might also want to take a look.

I have a lead regarding the Accessibility issue now, I will see whether I can do something about it.

Thanks, testing on canary and looking good so far 👍😊Can't tell with regards to Accessibility service since I've always used Autofill API exclusively.

[fmeum]

@andreaippo You might also want to take a look.
I have a lead regarding the Accessibility issue now, I will see whether I can do something about it.

Thanks, testing on canary and looking good so far Can't tell with regards to Accessibility service since I've always used Autofill API exclusively.

Autofill in Chrome uses Accessibility under the hood, so all issues with Accessibility (such as degraded performance on large pages) are also present with Autofill.

[fmeum]

@fmeum

https://bugs.chromium.org/p/chromium/issues/detail?id=1014945

Is this still an issue with latest canary version? Is your password manager also affected?

This should be fixed in 89.0.4356.2. Please give it a try and report back.

[quthla]

@fmeum
https://bugs.chromium.org/p/chromium/issues/detail?id=1014945
Is this still an issue with latest canary version? Is your password manager also affected?

This should be fixed in 89.0.4356.2. Please give it a try and report back.

You're incredible! But what a disgrace on the Chrome devs who weren't able to fix this or didn't even care at all about such a serious issue.

Thanks

[Shaunakde]

I'm on Chrome 87.0.4280.101

I recently wanted to try out Dashlane, and I migrated some passwords to it. It seems to work with Android Autofill and this version on Chrome. I've attached some screen shots to show this.

[johns2s]

@fmeum Do you have a link to the issue tracking the work to allow saving passwords?

[fmeum]

@fmeum Do you have a link to the issue tracking the work to allow saving passwords?

The issue is 1151614. The associated commit will land in Chrome 89 and exposes the unmasked passwords to Autofill services as long as no Accessibility service is enabled. The exact condition can be found in WebContentsAccessibilityImpl#isCompatAutofillOnlyPossibleAccessibilityConsumer().

[yurividal]

This seems to be working on Chrome 89.
I'll continue to test and report back if it stops working after a while.

[ChristianAziz]

Thanks @fmeum!
Can confirm. After updating to Chrome 89, inline-autofill works every time as expected.