Issues with 1Password for Safari

Hello @aviel! 👋

I'm sorry that you're running into issues with 1Password for Safari. Thanks for sharing the link to the conversation on Threads, a member of our development team has reached out there directly and is looking into the issue that the original poster reported. I've also reviewed the wider conversation and it looks like the issues being reported by folks are known to the team and already under investigation.

Sometimes the extension won’t open, sometimes it opens but locked and won’t respond even though the regular 1p app is unlocked and despite setting it to never lock, sometimes it won’t autofill, sometimes the thing below the text field showing options won’t work, etc

Just to clarify, are these all issues that you're running into personally? Have you run into all of these issues while running the latest version of 1Password for Safari (2.23.3)? I want to make sure that I understand the issues that you're seeing.

The team is aware that the experience with Safari isn't where it should be and work is ongoing to make the experience more stable. The reason why my colleagues and I ask folks to send in logs is because there are multiple open issues with similar symptoms and the logs help our team identify which specific issue someone is running into. Once the specific issue is identified we can then suggest a specific fix or workaround for that issue. I know that it can be time consuming to send in logs but it's the best way for us to identify which specific issue you're running into and then provide suggestions for your specific situation until a permanent fix is developed and released by our development team in a future update.

I look forward to hearing from you.

-Dave

Thank you for the response, I appreciate the details!

Just to clarify, are these all issues that you're running into personally? Have you run into all of these issues while running the latest version of 1Password for Safari (2.23.3)?

Yes and yes

One thing to note - all of those issues (1p extension locked and can’t unlock while 1p app is unlocked, auto fill not working, etc) are resolved once I quit and relaunch Safari - which is the workaround I’ve been doing thus far. Also - once it works, it stays solid for a few days, then problems come again.

This makes me think it’s not an issue with parsing the html or listening to events from Safari etc, but a corrupted state that the app reaches to after being open for multiple days (I never turn off my mac or quit Safari unless I hit those issues…).

Maybe as a temp relief there can be some backdoor feature to “blow up” (ie reset) the Safari extension state whenever this happens? - even a command line command can be great!

Hope this helps somehow! Thanks again

@aviel

Thanks for confirming that you're still running into the issues that you mentioned, I'm sorry again for the frustration and impact that these issues are causing.

This makes me think it’s not an issue with parsing the html or listening to events from Safari etc, but a corrupted state that the app reaches to after being open for multiple days

The bulk of the issues surrounding Safari currently involve the integration between 1Password for Safari and the desktop app. This integration is a unique feature that isn't shared by most other extensions and it can sometimes run into problems. Turning off the integration should improve the situation quite dramatically:

1. Open Safari.
2. Right-click on the 1Password icon in Safari and click Settings.
3. Turn off "Integrate this extension with the 1Password desktop app."
4. Repeat step 2 and 3 for all Safari profiles.

With app integration turned off you'll need to unlock 1Password in each profile separately and you'll need to use your account password (Touch ID and Apple Watch unlock won't be available).

I know that this isn't the best workaround but I wanted to share it in case it helps.

-Dave