Safari extension still very slow to unlock :-\

Hi cortig, my apologies that this problem continues to rear its head for you (and the other folks in this thread). I'll follow up with the appropriate team here about the status of this issue and will hope to have more for you shortly. Thank you again for your patience!

ref: dev/core/core#16362

This thread is about a year old now and still no improvement (on the contrary).
It takes between 30s and a minute on Ventura to unlock the Safari extension when the extension and the app are integrated.
Is there any update on the issue 1P_PeterG ?
Is it an Apple bug or a 1Password issue??

Same thing for me, once unlocked, things are fine, but it takes forever to unlock. I had to tweak my settings to extend now long I keep things unlocked on the Mac because I couldn’t take it anymore (which, on a safety standpoint, is obviously not great…)

I'm experiencing this same issue. In fact for me, I have never seen the Safari extension recognize that I have successfully entered my credentials to open 1Password - it just sits there with the "Open in 1Password" button. I have always had to click on "Open In 1Password" again to have it populate. Once unlocked response times are generally good.

In addition to this, when 1Password is locked and I click on the 1Password Safari extension icon sometimes (10-20%) of the time 1Password app opens automatically for me to enter my credentials but most times nothing happens and I need to click on "Open in 1Password" to bring up the app so I can enter my credentials.

+1 Safari extension is a total pig on 1st open. Firefox, Edge work fine.

Coming back to this issue… 39 seconds between the moment I unlock the app and the moment I can actually use my passwords in Safari. Obviously there is still a problem of communication between the app and the Safari extension. Any update 1P_PeterG ??

Corentin

Any progress on this front?? Unlocking 1Password for Safari remains really slow (and we're 8 months later now…). I'd love to know a bit more about what's going on.

Thanks for the follow-up, snozdop. We are looking into this issue, and your description does help (and fwiw, this does not sound like a resource issue to me - there's some digging we need to do on this one, but it doesn't appear to be an issue of, for example, 1Password demanding a lot of memory that the system can't provide). Thanks for helping us better understand this as we continue the process on our end.

Do you think this might be an available-resource issue on the system generally, or does the problem seem to be specific to 1Password?

Even after a fresh reboot, with almost nothing else running (just a few menubar apps that start at login) it's the same. My Mac mini has 16GB RAM and is running macOS Catalina 10.15.7 with Safari 15.3. I know it's considered old and slow by today's standards but 1Password 7 is pretty much instantaneous.

It seems to be worse on the first unlock after a period of not being used. Once it's unlocked it's mostly ok. And the sequence of events logging in isn't always the same. For example, this morning I got the prompt in Safari to Unlock 1Password (the app), which I did and then the Safari extension prompt was asking me to unlock 1Password from the toolbar. I did this too and then it got stuck on "Loading...", for minutes. Eventually I managed to get it to work by toggling the extension off and on and logging in yet again.

Thanks for the confirmation, @corentin 👍