Forum Discussion

Tezcatlipoca's avatar
Tezcatlipoca
Occasional Contributor
11 months ago
Solved

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 Autofi...
macos
  • 1P_Dave's avatar
    1P_Dave
    3 hours ago

    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 a fix in the nightly version of 1Password, if testing goes well the fix 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 fix then you can try the nightly here: 


    If you'd like to avoid using the nightly, and wait for the fix 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 soon as the fix is available in the production version of 1Password for Mac. 

    -Dave

bwadm's avatar
bwadm
Dedicated Contributor
7 months ago

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's avatar
1P_Dave
Icon for Moderator rankModerator
7 months ago

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