Forum Discussion

jonsuh's avatar
jonsuh
New Contributor
3 days ago

Universal Autofill + Chrome extension not working with latest Chrome on macOS (142.0.7444.60)

With the latest update of Chrome on macOS, Universal Autofill’s CMD+\ is no longer working properly with the Chrome extension.

Problem: CMD+\ does not automatically autofill form fields on any website.

Instead, you see the “Search 1Password” quick access popup, which indicates it does not detect the website you are on when you press CMD+\

  • macOS version: Sequoia 15.7.1
  • 1Password for Mac version: 8.11.16 (81116035 on PRODUCTION channel)
  • Google Chrome version: 142.0.7444.60
  • 1Password extension version: 8.11.16.35

Additional troubleshooting information:

  • 1Password “Connect with 1Password in the browser” is checked/enabled
  • 1Password extension “Integrate this extension with the 1Password desktop app” is enabled and “Integration status” shows “Connected 🟢”
  • The following does not fix this problem:
    • Quitting 1Password and Chrome, and restarting both
    • Removing and reinstalling the 1Password browser extension
    • Restarting my computer
  • 1Password Beta extension version 8.11.18.30 has the same problem
browser extension

7 Replies

  • Steamboater's avatar
    Steamboater
    Occasional Contributor
    6 hours ago

    Came here to post same. CMD \ used to autofill browser forms now brings up search 1pw and wants to set main pw for Chrome app not browser. 

    Chrome 142.0.7444.60 (Official Build) (arm64)

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    2 days ago

    Hello jonsuh​, superuser_22​, and reub​! 👋

    I'm sorry that Universal Autofill isn't working in Chrome. There is a known issue where Universal Autofill isn't working correctly with recent versions of Chromium. The issue affects all Chromium-based browsers including Chrome. 

    I've added your report to the internal work item for the issue. For the time being, as a temporary workaround, I recommend using 1Password in the browser (the browser extension) to fill your logins in Chrome by clicking on the suggestion that appears on the page rather than using the keyboard shortcut. Alternatively, non-Chromium browsers like Firefox and Safari don't experience the same issue. I'm sorry for the disruption caused. 

    -Dave

    Issue=FS-388

    • jonsuh's avatar
      jonsuh
      New Contributor
      23 hours ago

      1P_Dave​ Thanks for the update. I figured that was the case—I tested with Brave too, which is Chromium-based, and it has the same problem.

      When you know more, a follow-up would be great, esp to know if it’s something that would be fixed with a 1Password or browser extension update; or requires a Chrome update due to a Chromium bug or change.

  • reub's avatar
    reub
    New Contributor
    2 days ago

    Same issue (and same versions).

  • jonsuh's avatar
    jonsuh
    New Contributor
    3 days ago

    Not sure if this is related, but I checked the extensions’s console log, and it’s littered with these errors and warnings:

    • ❌ Unchecked runtime.lastError: The message port closed before a response was received.
    • ❌ Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    • ⚠️ background.js:80 DeviceTrust: access denied: [ missing backoffice permission, missing admin permission ] - aborting

    (For the access denied warning, I checked and the extension has “Site access Allow this extension to read and change all your data on websites you visit:” set to “On all sites”)

    Additional follow-up info:

    • CMD+\ autofill works properly with the latest versions of Mozilla Firefox (144.0.2) and 1Password browser extension (8.11.15.5)