Skip to main content
Tezcatlipoca
Apr 13, 2025 1:39 AM UTC
Question

Universal Autofill and Quick Access aren't working in Chromium browsers like Chrome and Brave

  • macOS Sequoia 15.4
  • 1Password for Mac 8.10.70
  • 1Password extension for Edge, Version 8.10.70.27
  • Microsoft Edge Version 135.0.3179.54 (Official build) (arm64)

Autofill / Universal Autofill no longer works! 🥲

CMD \  no longer works - it just brings up Quick Access.

Nothing's been changed in any settings - Autofill is still enabled, CMD \ is still enabled, etc.

104 replies

Apr 13, 2025 6:58 PM UTC

Same issue, except my problem is with Safari. This needs to be fixed pronto. I now have to create numerous Keyboard Maestro macros to get around the 1 Password problem. 

Tezcatlipoca
Apr 15, 2025 9:11 PM UTC

Just updated to the latest version of 1Password for macOS that was released today, 8.10.72.

Not fixed! 🥲

1P_Dave
1Password Employee
1Password Employee
Apr 17, 2025 8:14 PM UTC

Hello @Tezcatlipoca, @bwadm, and @JerrySG! 👋

I'm sorry that Universal Autofill isn't working correctly, this is a known issue that I've been able to reproduce as well and a bug report has been filed with our development team to get this fixed. I've added all of your reports there. 

For the time being, as a temporary workaround, please use 1Password in the browser to fill your login credentials in the browser: Get to know 1Password in your browser

When it comes to other apps, you can copy and paste your login credentials from the 1Password app. Hopefully this will be resolved soon.

-Dave

bwadm
Apr 18, 2025 7:39 AM UTC

Hi Dave, 

I have "1P for my Browser" (that is, the 1Password for Safari.app version 8.10.70) installed and connected. The small icon does show up in the username/pwd fields. BUT: it does not fill! 

It did before the update to 15.4 (now 15.4.1).

1P_Dave
1Password Employee
1Password Employee
Apr 22, 2025 2:21 PM UTC

@bwadm 

I've replied to your other post, let's continue the discussion there. 

-Dave

Tezcatlipoca
Jul 29, 2025 9:39 PM UTC

https://releases.1password.com/mac/beta/#1password-for-mac-8.11.4-25

  • We’ve fixed an issue where Universal Autofill for macOS wasn’t working for apps or websites.

Nope! 🥲

 

Jul 30, 2025 1:35 AM UTC

Yep...it is absolutely crazy to me that this has been going on for months now without resolution. My credit card isn't going to work when it comes time to renew 1password. 

 

bwadm
Jul 30, 2025 3:14 PM UTC

Since I updated to macOS 15.6 (new version of Sequoia) a few hrs ago, the issue with the Safari extension seems gone / fixed. In parallel to the system update, the 1P main app was updated to 8.11.4 (81104025 BETA). I did a save boot after the updates (also Adobe, MS Office and some other App had updates.). 

I hope that my assumption holds true also after prolonged testing. 

1P_Dave
1Password Employee
1Password Employee
Jul 30, 2025 6:18 PM UTC

@bwadm 

Thank you for the report! I'm also no longer able to reproduce the Safari extension autofill issue after updating to macOS 15.6 which does seem to suggest that the fix is now in the stable version.

Our team is currently testing this further in order to confirm that the issue is now fully fixed. 

-Dave

Aug 12, 2025 3:45 PM UTC

I can't use cmd-\ to bring up the normal 1P prompt in MS Edge/Mac.  I use that instead of the browser-based drop downs, and have for years.

This started recently, possibly with an Edge update.

It works fine with Chrome, also up to date.

It happens on two Macintosh computers: one a 2017 iMac (Intel), and the other a year-old Macbook Pro M3.  Edge doesn't work, Chrome works.

Does anyone have any thoughts?

---------------

2017 iMac
MacOS 13.7.1

1Password for Mac 8.11.4
81104027, on PRODUCTION channel


MS Edge/Mac
Version 139.0.3405.86 (Official build) (x86_64)
1P extension
Version 8.11.4.27

Chrome/Mac
Version 139.0.7258.67 (Official Build) (x86_64)
1P extension
Version 8.11.4.27

- - - - - - - -

2024 Macbook Pro M3
MacOS 14.6.1

1Password for Mac 8.11.4
81104027, on PRODUCTION channel

MS Edge/Mac
Version 139.0.3405.86 (Official build) (arm64)
1P extension
Version8.11.4.27

Chrome/Mac
Version 139.0.7258.67 (Official Build) (arm64)
1P extension
Version 8.11.4.27

 

1P_SimonH
Community Manager
Community Manager
Aug 12, 2025 8:50 PM UTC

Hi @aemerson,

Thanks for reporting this! 

Just to make sure I'm understanding this: On Edge, you have the 1Password extension installed, but when logging in, your preferred workflow is to use cmd-\ to bring up Quick Access and select which login to fill with. As of a few weeks ago, though, cmd-\ doesn't do anything. Please correct me if I got any of that wrong!

Could you please take a screenshot of your 1Password extension autofill settings and post that here? To get to that window, select the puzzle piece icon in an Edge window, click the three dots to the right of 1Password in the list of browser extensions, then select Settings and then Autofill and Save.

Thank you! 

1P_Dave
1Password Employee
1Password Employee
Mar 26, 2026 7:30 PM UTC

Hello folks,

I'm sorry for the trouble caused by an issue where Universal Autofill isn't working correctly in Chromium browsers like Chrome and Brave. The team and I appreciate all of your patience while we looked into the issue. Our development team is currently testing improvements in the nightly version of 1Password, if testing goes well the improvements will be released to the beta and then to the production version as soon as possible. If you'd like to help us test the improvements then you can try the nightly here: 


If you'd like to avoid using the nightly, and wait for the improvements to be released to the production version of 1Password then you can continue to use 1Password in the browser to fill your login credentials instead: Get to know 1Password in your browser

We'll update this post as testing progresses in the nightly version of 1Password. 

-Dave

Apr 9, 2026 1:45 PM UTC

Hi @1P_Dave 

How is the testing going? Is the fix in beta or still in the nightly build?

1P_Dave
1Password Employee
1Password Employee
Apr 9, 2026 2:33 PM UTC

@prox 

Thanks for reaching out. We've found some issues that are still unresolved that our team is currently investigating. When a fix is available in the beta and production version I'll make sure to update this thread. 🙂

-Dave