Mac beta 8.10.7 (81007001) introduced severe bug, keeps crashing/closing

Sounds good.

1P_Tommy I have planned to upgrade my machine to 14.3 over the weekend. I'll let you know how it goes.

cryptochrome

The only thing I notice is I am on 14.3 and you're on 14.2.1. If you have a chance and you're ready to update you might give that a try. Other than that all looks the same. Haha, if I had noticed I would have put it together with your handle. I just got a good DOH! moment out of it.

Hey 1P_Tommy

I am using Chrome (currently 121.0.6167.75) and I am on macOS 14.2.1 (23C71). 1P browser extension sits on 2.19.0 (21900005, on STABLE channel)).

Let me know if you need anything else. Happy to help!

cryptochrome

On behalf of Dave you're welcome.

Thank god for Bartender

Haha I'm right there with you.

Mind if I ask which browser you're using? I saw an improvement with the update. Back when you opened this you were using 13.3.1 what OS version are you using now? I'm not sure that has an bearing. If you'd rather not pursue this then no worries.

Hello 1P_Dave

I had actually completely forgotten about this. So, the fix you implemented now doesn't seem to have any effect on the behavior described back in March.

I just updated to 8.10.24, made sure my browser extension is also up to date, disabled the 1P menu bar item and closed the 1P window. The browser extension immediately lost its connection to 1P (lock symbol on the icon) and all 1Password processes quit, with the exception of the 1P crash handler and the 1P browser helper.

When re-opening 1P desktop, it asks me for my master password, indicating further that it completely shut down on the window close event.

So from my perspective, nothing has changed.

This is not super important to me anymore, as the workaround (enable the 1P menu bar item) works fine and doesn't bother me (thank god for Bartender).

cryptochrome

I hope that you're doing well! Our developers have incorporated improvements to the unlocking process with the latest update to 1Password that should resolve the issue that you reported here. Can you update to the latest version (8.10.24) and try to reproduce the issue again:

• How to keep 1Password up to date

If you still see the issue after updating and restarting 1Password then please let me know.

-Dave

ref: dev/core/core#22007

cryptochrome

Thank you again for reporting the issue. If our developers do need any other information from your end then we'll make sure to reach out. Hopefully this will be fixed soon. 🙂

-Dave

ref: dev/core/core#22007

1P_Dave - yep, pretty much the same behavior under the same conditions here. It's almost like it crashes (but it doesn't, the processes are still running).

Thanks for getting this filed!

If you guys need anything, like logs, shoot me a message.

cryptochrome

I'm sorry for misunderstanding. I can reproduce that issue myself if try to unlock 1Password from the browser extension while using my account password. But I can still unlock the desktop app if I launch it from the Applications folder and not from the browser. Alternatively, unlocking 1Password using Touch ID (instead of the account password) also avoids the issue.

And the issue does not occur if "Keep 1Password in the menu bar" is enabled (although the main window does close after 1Password is unlocked which is an existing known issue).

Is this the same behaviour that you're seeing on your end? I'm filing an internal work item for the bug so that our developers can investigate further and I'll add your report there.

-Dave

ref: dev/core/core#17554