Browser extension always prompt for password after 8.10.38 update

pkr2
pkr2
Community Member

I got the message "Some of your settings have been reset" which disabled touchId and AppleWatch unlock, until I hit the "Advanced" -> "Reset 1Password" button, which managed to restore touchId and Apple watch unlock.

Now all my browser plugins (chrome, brave, safari) are asking for password instead of being unlock with the 1Password application.

I have checked that all browser are up to date - as it used to be the case that a pending update would block the unlock, but they are all up to date.

How can I re enable browser plugin unlock with the main app?


1Password Version: 8.10.38
Extension Version: 2.26.1
OS Version: macOS 14.5
Browser: Chrome

Comments

  • pkr2
    pkr2
    Community Member

    After having issue reconfiguring the ssh-agent, I rebooted my laptop and now the 1password app keep getting the focus when a browser is in used, making it unusable

  • Hello @pkr2! 👋

    I'm sorry that you're running into a few different issues after updating 1Password to the latest version. Regarding the Settings Reset message, please see the explanation that I posted here: https://1password.community/discussion/comment/715748/#Comment_715748

    I rebooted my laptop and now the 1password app keep getting the focus when a browser is in used, making it unusable

    This is a known issue with the latest version of 1Password that our developers are currently working to resolve and involves the connection between the desktop app and 1Password in the browser. You should be able to workaround the issue by following these steps:

    1. Open and unlock 1Password for Mac.
    2. Click on 1Password next to the  in the menu bar.
    3. Click Settings.
    4. Click Browser.
    5. Turn "Connect with 1Password in the browser" off and then back on.

    Let me know if that doesn't work.

    -Dave

    ref: dev/core/core#29392

  • pkr2
    pkr2
    Community Member

    yes that's what I did and it worked - thanks for the quick response!

  • @pkr2

    I'm happy that the steps helped you to workaround the issue. 🙂

    -Dave