Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
baikunz
3 months agoNew Contributor
Ongoing Autofill Issues on Android
Hi, I've been a long-time user of 1Password, and up until recently, the experience has been excellent. However, for the past few months, the Android experience has significantly deteriorated. Autof...
snoringelephant
3 months agoFrequent Contributor
I am following-up on my previous post (rather than replying) to say that I have found some settings that seem to have helped my autofill issues.
I first found this Reddit comment helpful (which also introduced me to chrome://flags which I had not known about).
Before setting the flags, I decided to ask Google Gemini about these settings (thinking it would provide a more insightful answer since Chrome is a Google product) and a third flag was also mentioned.
So, I ended up enabling the following three flags:
- #autofill-third-party-mode-content-provider
- #credential-management-third-party-web-api-request-forwarding
- #enable-autofill-virtual-view-structure
as such:
After restarting Chrome on my Android tablet, I tried a few websites and the "Open 1Password" option appeared more than I had seen it in the past and I was able to do more autofilling than I had been as well.
I am still testing, but these flags seem to have helped my situation.
- lauriel3 days agoNew Member
I cannot find the #enable-autofill-virtual-view-structure and I wonder if that is my missing piece? I haven't found a flag configuration of the other two that works most of the time. If it doesn't work, before manually entering in the information, I change the flags. This works often, but no in all cases.
I have been a user for many years and I am very tired of this not working on android.- sjmoll3 days agoNew Contributor
Based on the info provided, we should disable any of these flags as they will eventually not be supported with the updates from Chrome and 1password. My guess is that they seem to work when you enable them just bc that will restart Chrome. So i would try just doing a restart. I agree it's frustrating, especially since Chrome made this change and then is taking so long to release a fix.