1Password for Safari not communicating with the desktop app [FIXED]

Okay, thanks all.

Hi WayneV

Apologies for the trouble you're experiencing with 1Password for Safari not sharing the same lock state as the desktop app on your Mac. As shrimppesto pointed out, this is a known issue that's on the radar of our development team and they're working on releasing a fix for this issue that arose over the last few days. You can keep an eye out for updates regarding this issue on the 1Password Status website here: 1Password Status - SLS not working in Safari.

In the meantime, you can continue unlocking 1Password for Safari manually before being able to continue using it to create, fill, and save information on the web. The 1Password browser extension and integration with the desktop app is also working fine in all other non-Safari browsers in case you would like to temporarily switch over to Chrome or Firefox until this fix is available.

Hi gaolson

I do apologize for the trouble you've encountered with 1Password for Safari on your Mac where you're no longer able to unlock it with Touch ID. As dragon1 has pointed out, this is a known issue that arose over the weekend and the team are working on a fix to be released as soon as possible. You can keep an eye out for updates regarding this issue on the 1Password Status website: 1Password Status - SLS not working in Safari.

In the meantime, whilst waiting for a fix to become available, you can manually unlock your 1Password account in 1Password for Safari before being able to use it as normal. Alternatively, you can use another browser like Chrome or Firefox since the integration between the 1Password browser extension and the desktop app is working as normal there.

Hi jazzman

Apologies for the trouble you're experiencing no longer being able to unlock 1Password for Safari with Touch ID on your iMac. This is due to an unexpected issue that arose over the weekend but the development team have identified the root cause and are working on a fix for this bug. I recommend keeping 1Password for Safari updated and keeping an eye out on the incident page for updates:
- How to keep 1Password up to date in your browser
- 1Password Status - SLS not working in Safari

In the meantime, you can manually unlock 1Password for Safari with your account password and use it as normal until a fix is available to resolve the broken integration. You can also switch to another non-Safari browser as the 1Password browser extension and integration to the desktop app is functioning as normal there.

Hi stein

Apologies for the trouble you've encountered with 1Password for Safari where the integration to the desktop app has stopped working. As danco mentioned, this is a known issue that popped up over the weekend and the development team have been hard at work investigating.

The good news is that the root cause has been identified and a fix is in the works as we speak. We're hoping to have this available as soon as possible so be sure to keep 1Password for Safari updated on your Mac and you can keep an eye out for developments on the 1Password Status website:
- How to keep 1Password up to date in your browser
- 1Password Status - SLS not working in Safari

Hi everyone! JerrySG dragon1 asrob BrainD tetardbleu dcrdev JasonN dtoub

Apologies for the silence over the last day since Kevin provided you all with an update on this issue in 1Password for Safari. Today is Labor Day in the US & Canada which meant most of my colleagues have been away from their computers over this long weekend.

The good news is that the development team have identified the root cause of the issue that randomly broke the integration between 1Password for Safari and the desktop app and are working on getting a fix out as soon as possible. This wasn't due to a bug in an new update by 1Password or macOS so no faulty updates are at play here.

There's some final things for the team to check over once folks come back into the virtual office from tomorrow but you can keep an eye out for developments on the 1Password Status website: 1Password Status - SLS not working in Safari.

This hiccup in the integration only affects 1Password for Safari which means you can continue using it and unlock your 1Password account manually each time Safari closes and reopens until the fix is available. Alternatively, you can temporarily switch over to another browser where the 1Password browser extension integration to the desktop app is still working as expected.

Hi ChrisJenkins & cvadmin

Apologies for the trouble you're experiencing with 1Password for Safari on your Mac where your security settings are out of sync between the 1Password browser extension and desktop app. The development team have been made aware of an issue that arose with 1Password for Safari over the weekend which broke the integration between the two and are working on a fix.

We're pushing to have this fix available on the App Store as soon as possible but you can continue unlocking 1Password for Safari manually after Safari is re-opened or you can temporarily switch to another browser like Chrome or Firefox since the 1Password browser extension isn't affected there.

You can also keep an eye out for developments on the 1Password Status website here: 1Password Status - SLS not working in Safari.

Same problem here. When I first noticed the problem, every time I would type my password to unlock 1Password for Safari it would open the 1Password login page on a new tab. Eventually I went ahead and signed in there and now at least that doesn't happen every time, but Touch ID and Apple Watch unlock no longer work, nor does unlocking the 1Password app. It requires manually typing the password in Safari.

1Password 8.10.40
1Password for Safari 2.27.1
Safari 18.0
macOS 14.6.1

I have the same issue. This is really beyond comprehension that 1Password is overriding a user's control of decisions that they have already made. It is burning time of the end-user for absolutely no gain in security except from the user who already logged into their machine.

Revert this change!

I literally came here to report this issue and am glad it is known and a fix is in process.