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 reliable autofill experience.What does this update do?We’ve updated how 1Password integrates with Chrome and Brave, aligning with recent changes introduced by the Chromium team at Google. These changes aim to provide a more stable, native autofill experience, and will replace the older "compatibility mode" approach.If you’re using the latest versions of Chrome (v135+) or Brave (v1.79.119+) and 1Password (8.11.4), you’ll now get a more reliable autofill experience once your browser is properly set up to integrate with 1Password.Important: Please follow all the steps in our user guide carefully, even if you have previously enabled autofill on Android, as the necessary settings have changed.Why has autofill on Android been so unreliable lately? Google’s Chromium team rolled out changes over the past few months that are designed to improve users' autofill experience. Overall these were welcome improvements, but they introduced growing pains for third-party password managers:Chrome deprecated the “compatibility mode” approach to autofill that 1Password relied on, replacing it with a new, native autofill integration. (The same kind of integration 1Password already uses in other Android apps.)Additionally, Chrome now requires users to opt-in to a new setting to enable autofill support for third-party password managers, even if autofill was previously working in the browser.All of that is to say that there has been a dramatic change, for the better, to how autofill works under the hood in Chrome. But the new experience rolled out unevenly on the Android side, and it also required some additional changes to 1Password, leaving many users in an in-between state with broken autofill during the transition period.In our attempt to prepare users for these changes, we published a post last week that ended up causing additional confusion. We took this step to prevent users from experiencing a complete loss of autofill functionality following the release of today’s update (8.11.4). In retrospect, we probably should have released that messaging at the same time as the update.What about these browser feature flags?Some users may have previously used browser flags to force the deprecated compatibility mode to work. That approach may have provided some relief, but we advise against it as it will break autofill with 1Password going forward.If you’ve changed any flags, we strongly advise resetting them to their defaults:Open chrome://flags or brave://flags in your browserTap Reset all in the top-right cornerRestart your browser when promptedAutofill might still appear to work with some flags enabled, but we can't guarantee future compatibility. Now that the native integration is fully implemented in both Chrome and 1Password, we strongly encourage users to reset those flags to their default settings to get the most out of this update.Please use this thread to share your experience with this update and to ask any questions you may have about 1Password on Android.

1Password Employee

Solved

Major autofill update on 1Password for Android

Forum|Forum|11 months ago
August 5, 2025
18 replies
4602 views

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 reliable autofill experience.

What does this update do?

We’ve updated how 1Password integrates with Chrome and Brave, aligning with recent changes introduced by the Chromium team at Google. These changes aim to provide a more stable, native autofill experience, and will replace the older "compatibility mode" approach.

If you’re using the latest versions of Chrome (v135+) or Brave (v1.79.119+) and 1Password (8.11.4), you’ll now get a more reliable autofill experience once your browser is properly set up to integrate with 1Password.

Important: Please follow all the steps in our user guide carefully, even if you have previously enabled autofill on Android, as the necessary settings have changed.

Why has autofill on Android been so unreliable lately?

Google’s Chromium team rolled out changes over the past few months that are designed to improve users' autofill experience. Overall these were welcome improvements, but they introduced growing pains for third-party password managers:

Chrome deprecated the “compatibility mode” approach to autofill that 1Password relied on, replacing it with a new, native autofill integration. (The same kind of integration 1Password already uses in other Android apps.)
Additionally, Chrome now requires users to opt-in to a new setting to enable autofill support for third-party password managers, even if autofill was previously working in the browser.

All of that is to say that there has been a dramatic change, for the better, to how autofill works under the hood in Chrome. But the new experience rolled out unevenly on the Android side, and it also required some additional changes to 1Password, leaving many users in an in-between state with broken autofill during the transition period.

In our attempt to prepare users for these changes, we published a post last week that ended up causing additional confusion. We took this step to prevent users from experiencing a complete loss of autofill functionality following the release of today’s update (8.11.4). In retrospect, we probably should have released that messaging at the same time as the update.

What about these browser feature flags?

Some users may have previously used browser flags to force the deprecated compatibility mode to work. That approach may have provided some relief, but we advise against it as it will break autofill with 1Password going forward.

If you’ve changed any flags, we strongly advise resetting them to their defaults:

Open chrome://flags or brave://flags in your browser
Tap Reset all in the top-right corner
Restart your browser when prompted

Autofill might still appear to work with some flags enabled, but we can't guarantee future compatibility. Now that the native integration is fully implemented in both Chrome and 1Password, we strongly encourage users to reset those flags to their default settings to get the most out of this update.

Please use this thread to share your experience with this update and to ask any questions you may have about 1Password on Android.

Android

Best answer by 1P_SimonH

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.

Show previous replies

N

n00bio

Just jumping in here to reiterate that this definitely isn't solved. Might make sense to update the status from "Solved" to "Losing Customers Hourly" @patrick @1P_SimonH

D

Dblbassman

At the very least, a public aknowledgment of the failure!

N

n00bio

Android issue with Chrome and Brave is not fixed. Your guide sucks. You have one more week to acknowledge there's still a problem or I'm requesting a refund and moving to another password manager solution. Your app in the play store is already down to 3.9 stars with more 1 star reviews every day. Seriously what are you doing?

D

Dblbassman

Why is this thread still marked as "solved?" That's an affront to this "community."

AJCxZ0

See @1P_Dave's explanation and ensuing discussion in another post:

1P_DaveP wrote:
Marking a post as a solution to a thread doesn't mean that the issue itself is solved or closed. It's a way to highlight the most up-to-date answer to a thread (letting them know that this is a known issue that our team is investigating) for anyone who stumbles onto the thread in the future.

X

Xil

@n00bio As a user, I'm curious what some of your critiques of 1Password actually are. I find no issues with it and I use a number of browsers, including Brave, and experience no such issues.

Would be good to hear some of your critiques and insights... if you're still here seven days later...

N

n00bio

The experience on Android devices got screwed up with Chrome's update. Now passwords and logins don't fill in 90%-95% of the time. Quitting Chrome and closing all browsers sometimes works for a couple logins, but after a while, eventually it stops working again. Otherwise 1Password is great. The desktop experience is awesome. The browser plugins are awesome. The shared family vault and ability to share all passwords in real time as they're updated and changed is great. But Android/mobile devices are pretty critical and a lot of browsing time is spent there. It's slow and annoying to have to switch apps and manually copy and paste nearly every time I need to login to something.

X

Xil

I understand. And following the guide in this article hasn't helped at all? I run Apple devices, so it's a little different for me. But still, Brave/Chromium.

N

n00bio

Woohoo! Problem seems fixed now with beta Chrome. Thank you Agile Bits team!

N

n00bio

Thank you for the September 3 update Simon! I didn't get a notification this thread was updated since it was popped into your older solution, but I'm glad I caught it. Joining the beta program for Chrome and updating Chrome to the beta version seems to have fixed everything. Thank you for working with Google to get 1Password working as expected again!!

D

Dblbassman

Now using latest 1Password and Chrome beta. The oroblems persist. Next?

Oh, and marking this thread as solved is like declaring your car fixed because you turned up the radio to mask the engine noise or like placing an "Open" sign on a business with the doors locked.

patrickAuthor

1Password Employee

If you still have to restart Chrome periodically to get autofill to work, and you're on Chrome 141+, it's possible you're not in the testing cohort. You can manually enable the fix by opening chrome://flags and force enabling #autofill-update-context-for-web-contents

D

Dblbassman

Patrick-- Thank you! I am definitely in the testing cohort. I have enabled that flag within Chrome Beta. I'll see how it goes. Again, thanks for the information.

G

GSK

I'm a little late to the party here, but thought that I would mention that auto fill seems to be working for me. I'm on a Pixel 8 pro with android 16 using version 8.11.8. Chrome version 140.0.7339.123

Also, I'm wondering if I should be on 1password beta for Android or if I should take a "if it isn't broken, don't fix it" approach, and stay on the stable version.

What does this update do?

Why has autofill on Android been so unreliable lately?

What about these browser feature flags?

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded