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.

Here we are weeks later and it still isn't fixed. I've been back and forth with your tech support. I've sent reports, as requested, regarding various sites for which autofill still doesn't work. Several workarounds have been offered and discussed:Long-press the field, press the three-dot menu and select autofill. I've found that this works about 10% of the time. Sometimes, the autofill option isn't even there. Other times, it is and, if you're luck it'll bring up suggestions for filling. Selecting one often results in the fields not getting filled anyway.Close the Chrome browser, re-open it, and try again. This works about 40% of the time. Of course, closing the browser and having to navigate back to a site is extremely inconvenient and hardly a solution.Clear the Chrome browser cache and start over. Whether this works is pretty much hit and miss.As I mentioned earlier, none of this is acceptable as a paying customer. Cards on the table-- are you going to get this right any time soon?

patrick

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.

1P_SimonH

Community Manager

Tagging a few people who participated in our last discussion thread on this. That thread has been archived to avoid confusion and outdated information. Please let us know if you have questions or feedback!

@Threefish @Xabach @yanpurvenes @larrryjseltzer @AJCxZ0 @OLCE @robertb @alexmidd @ctaranto @QuozL

Threefish

For clarity, I presume "today’s update" for Android means version 8.11.4?

1P_SimonH

Community Manager

That's correct, @Threefish! I've added that to the post.

AJCxZ0

The link in the What's new section of the app points to a Community post rather than the guide, effectively denying access to everyone who doesn't have a Community account. That post isn't available, being redirected here and effectively censoring the post.
This post doesn't include the instructions on what to change.

Autofilling my credentials in my browser to log in here works perfectly, but the login process goes nowhere. I don't recall having any problem logging in this way before.

The second step 1 of Set up Autofill in the guide for the critical change is still wrong, with the article published 21 Jul 2025 still saying,

① Return to Settings > Autofill in the 1Password app.

despite this having been identified as very bad mistake some time ago in the censored thread.

Autofilling and signing in the the Community with ⊙ Autofill using another service in Chrome 138.0.7204.179 on Android 16 and 1Password 8.11.4 works normally. Autofilling no longer works with ⊙ Autofill with Google.

Good job with the app, @patrick and the Android devs.

AJCxZ0

With the release of the 8.11.6 version of the app a day or two later, the problem of the link to the (wrong) Community post in the What's new section has been fixed by virtue of it no longer being new.

As a result, anyone who did not catch the instruction in the What's new section during the few days it was current will have missed it. This isn't a 1Password problem, as unlike ~~Google~~ certain other app publishers, 1Password uses What's new properly.
Even so, I suspect that the fraction of folks who read What's new for every app update is small.

Given its breaking change nature, I think this deserves a one-time notification on first launch, though I don't bear the costs of coding it and handling the consequent support burden from folks struggling with it around the same time.

D

dave_

@patrick, thanks for sharing the news. Sounds like a win for Chromium-based browsers, but does this have any impact on Firefox on Android? Autofill there has been hit or miss for me (unlike on Windows, where it usually works). I don't know if that's been due to a problem with Firefox, 1Password, Gboard, or some other Android component. I usually have to open the 1Password app manually, search for the site, then copy and paste between apps.

That said, just now I was able to log in to 1Password Community in Firefox on Android 16 using autofill (got the button at the top of the keyboard). This was from the link in the 1Password 8.11.4 release notes. However, after logging in, I got "Access Denied" and was punted to the home page. (The redirect to this thread works fine for me on the desktop, where I wasn't immediately forced to log in.)

H

HNofX82

hello,

I am using latest version of Chrome, did all required changes as mentioned above. But I am not able to get any prompts to fill in login credentials for any website in Chrome ?

N

n00bio

Your instructions work once. Then if I open another website or do anything else, it stops working and I have to go through the motions again and again. Please acknowledge there's still a problem and say you're working on it. I love this service, but if auto fill doesn't work, then there's no point in subscribing.

patrickAuthor

1Password Employee

Hi!

This is definitely not a solution that we expect to be repeated in order to continue seeing success. Once you've changed your settings there should be no need to repeat the steps. Any additional information about your case would be helpful in identifying a problem with either 1Password or the website/app you're trying to fill into. For example, website, browser version, phone model, Android version, 1Password version, would all be useful.

H

HNofX82

Hello,

I am already communicating with 1password support regarding this issue, have send all details as requested.

ahayes

Hello. I'm glad you are working on this and trying to keep up with Android changes.

I am using 1Password 8.11.4 on Android 16 (BP2A.250705.008) and am not able to follow the "Set up Autofill" instructions in the https://support.1password.com/android-autofill/. Step 3 says to Tap Open Settings but I don't have that option. Attempting to toggle Autofill off and on to see if that helps seems to be broken (always shows as enabled when I enter that settings page even after toggling off and backing out of Autofill settings, Account Settings, Force Quitting, Clearing Cache, etc.)

I was able to see and select the "Autofill using another service" setting in Chrome but did not have an option to Restart Chrome as indicated in the guide.

I tried all of this again with the current 8.11.6 81106025 on BETA channel version without any change in behaviour.

I hope this helps.

1P_SimonH

Community Manager

Hi @ahayes,

I'm sorry the instructions still aren't working for you! Could you please email mailto:support@1password.com so we can take a closer look at what might be happening?

1P_SimonHAnswer

Community Manager

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.

ahayes

Maybe my feedback was too late to make today's revisions. The very first section was the one that I couldn't reproduce and seems identical today. I'm looking forward to some more reliable auto-filling on Android. Personally I use Firefox on my phone and its been hit and miss there too so doesn't seem strictly like Chrome/Brave flakiness to me. I'll stay on the Beta for a bit to keep an eye on things and report back if anything improves for me.

D

Dblbassman

No, it's not fixed. I'm using 8.11.5 on more than one Android device with Chrome. All settings are correct. In order for autofill to work, the Chrome cache must be repeatedly cleared. It's unacceptable to use paying customers as your beta testers. Please find the requisite expertise and get it done!

1P_SimonH

Community Manager

Hi @Dblbassman,

I'm sorry this has been so frustrating and we've definitely learned some lessons about the need to communicate these sorts of changes more clearly.

I saw you had a ticket about this issue, but it was prior to our newest Android release. Please email mailto:support@1password.com to create a new ticket so they can investigate why things still aren't working.

D

Dblbassman

Here we are weeks later and it still isn't fixed. I've been back and forth with your tech support. I've sent reports, as requested, regarding various sites for which autofill still doesn't work. Several workarounds have been offered and discussed:

Long-press the field, press the three-dot menu and select autofill. I've found that this works about 10% of the time. Sometimes, the autofill option isn't even there. Other times, it is and, if you're luck it'll bring up suggestions for filling. Selecting one often results in the fields not getting filled anyway.
Close the Chrome browser, re-open it, and try again. This works about 40% of the time. Of course, closing the browser and having to navigate back to a site is extremely inconvenient and hardly a solution.
Clear the Chrome browser cache and start over. Whether this works is pretty much hit and miss.

As I mentioned earlier, none of this is acceptable as a paying customer. Cards on the table-- are you going to get this right any time soon?

N

n00bio

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

D

Dblbassman

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!

Show more replies

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