It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
Autofill not working on Chrome in Android
Starting about a month ago, after 1Password showed a notice that I should set updated autofill on my Android phone to 1Password, which I did, autofill options from 1Password have stopped appearing on log-in pages in Chrome on my phone, except in rare occasion.
I've repeated these steps (all settings on my phone were already set correctly, but I toggled everything on and off to replicate the steps) to try to get 1Password autofill working in Chrome again, but there has been no change in the issue I'm experiencing on my phone.
15 Replies
Thank you, setting `#autofill-update-context-for-web-contents` to enabled on `chrome://flags` with Chrome v 141 seems to have improved things for me
this doesn't work for me also.
Hopefully, by this issue tracker, Chrome 141 version would have a fix. https://issues.chromium.org/issues/439553272
- 1P_Dave
Moderator
Hello craisin, sjmoll, crabtre, and dantheman! 👋
I'm sorry that you're running into issues when using autofill in Chrome. It's been some time since you posted (and I'm sorry for the delay in replying) can you check to see if you're still running into the issue after updating to the latest version of 1Password, Chrome, and Android for your device?
If you are still running into the issue then can you tell me the following:
- Does autofill always start working again (at least temporarily) after you force close your browser and then re-open it again: Find, open & close apps on Android - Android Help
- Does the issue occur in the main Chrome browser? Or in an in-app browser opened by another app?
- If you try using a non-Chromium browser like Firefox then do you see the same issue there?
I look forward to hearing from you.-Dave
Hi Dave, based on the chromium bug ShoxJeans posted, it looked like maybe this would be resolved in v141. I now have that installed, and maybe it is better, but it's definitely not completely working. Are there open bugs with Chrome you are still tracking?
Just realized there's a chrome flag required to enable the fix for now. I've turned that on and will see how it goes.
Hi Dave - Most of the time force closing works. Occasionally it doesnt for a particular site, but it doesnt seem consistent as to which, and I usually dont try force closing a second time, but for the times where i do, that seems to work.
It seems to vary as to when it stops too where it may work on one site but not another. In just trying now, one Sony site worked with no force close in a whole, and then a couple minutes later a different Sony site didnt work (both use the same login but use a different page for authentication).
I dont often use other browsers but have tried to test this in Firefox, and it does seem to work fine there although I may not be using it long enough to tell.
And last, I do see this for in-app browsers too that are using Chrome (eg: Google search, Gmail, etc).
Thanks, Shawn
Can you give us links to the Chrome bugs causing this (assuming they make them public as Firefox does). Would like to follow there if there are updates.
The issue is a bug with Chrome relating to the changes they made. You can do a force stop of Chrome with the newer setup, and it will start working again for a period. I have seen certain websites stop working sooner than others.
Came on here looking to see if I could find what the actual bug is on chrome to follow there for progress.
Excellent! And appears multiple people are confirming the fix in the beta version. Thank you.
I am also having the same or similar issue. I enable auto fill using another service, 1Password works for a while (could be a day, could be 30 mins) and then it stops working. If I switch back to Google Auto fill, restart Chrome, and then switch back to Autofill Using Another Service it starts working again.
Very Frustrating.
I'm experiencing the same thing. On a Galaxy S25 Ultra and a Galaxy Tab10. Very frustrating.
