Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
patrick
1Password Team
2 months agoMajor autofill update on 1Password for Android
Hi! I'm Patrick, an Android developer here at 1Password. I'm happy to announce that we've made some changes to how 1Password interacts with Chrome on Android that should result in a much more reliabl...
- 2 months ago
Hi all,
We've updated the instructions today (August 7, 2025) based on feedback we've received here and elsewhere to try and take into account folks setting up 1Password autofill on a new device and for folks who have already been using 1Password. We'll keep making updates if you have additional feedback!
Update on September 3, 2025:
Some users are still seeing autofill issues in Android. We're working with our friends at Google to troubleshoot this. Google is aware of the issue and the fix is expected to arrive in beta versions of Chrome in September. For the more technically-minded folks, you can track progress here.
n00bio
2 months agoNew Contributor
Definitely frustrating. I sort of stumbled on the Chrome quitting solution myself and find it to work 100% of the time for the first login to whatever site. But then if I open another tab and go to a different site requiring a login, then that is hit or miss. Mostly miss. I think it was Chrome that messed everything up, so I'm trying to give 1Password some grace on this. But yes, it would be appreciated to see a stronger sense of urgency and communication on this...
Adding for fun: I created an account here only to request this be fixed and found it ironic and hilarious that I couldn't get autofill to work on this site, of all sites. ๐
Dblbassman
2 months agoNew Contributor
Chrome did not cause this mess. The mess is owned by 1Password. The impending change was known to developers. 1Password claimed they had made the appropriate adjustments and updates. They didn't. One wonders how they could have, in good conscience, made that claim if they had done any reasonable testing at all. Having failed at that, even after weeks and more updates, they still can't manage to get it right. I'm not aware that other services are suffering similar issues. I was happy to cut them some slack. No more! We're all still paying our subscription fees IN FULL. We're not receiving the promised services IN FULL. ENOUGH!