Issues with 1Password for Safari

aviel
aviel
Community Member
edited May 21 in 1Password in the Browser

For the last year or so (maybe since the infamous switch to electron? Not sure) the experience on Safari has been broken in more and more novel ways.
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
I’m not alone. Here’s a thread full of a lot of people complaining about the browser extension being broken in creative ways, seems like specifically in Safari more than all other browsers: https://www.threads.net/@chrisfree/post/C7CtRJnqyYe/?xmt=AQGzuHKQ46axLtmh5gX7AGXn4vukRbCvl-14P1dfxKyYYA

You must be doing something about this? Working on a rewrite or a fix beyond just monkey patching? Please?

I would love if whoever responds from 1p won’t ask me for yet more logs and screenshots of specific bugs - just go read the thread I linked - or use the extension on safari for more than a couple days - I promise the bugs will pile up. Also please don’t respond with “thoughts and prayers” style answer, I would really appreciate honesty here because this has been going for a year and is only getting worse and is the core of this product.
Thank you 🙏

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Comments

  • Dave_1P
    Dave_1P

    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

  • aviel
    aviel
    Community Member

    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

  • Dave_1P
    Dave_1P

    @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