Slow unlock in Safari when not using Personal profile

Thanks Kevin.

Since your post I've run the test a couple of times, each with and without the console displayed. When the console is displayed, the delay does not happen.

Will it still be useful to get a copy of the console log?

The exact steps I'm following:

1 - Exit Safari
2 - Exit 1Password completely
3 - Start 1Password, cancel the prompt to login, exit the main application, leave the menubar application running
4 - Start Safari, opening a single window initially set to the problematic profile
5 - Open the console or don't open the console
6 - Click on the extension button and use touch id to unlock
7 - If I didn't open the console there is a ten second delay for the unlock to happen. If I did open the console, there's a subsecond delay for the unlock to happen.

Let me know if you still want the log.

Thanks Kevin. I should have been more precise.

Before I begin any experimentation, I already have two profiles: "Personal" and "Trusted". To trigger the delay, I exit Safari with a single window open set to "Trusted". When I start Safari as part of the test, it opens with a single window set to "Trusted". I do not manually open a window or switch profiles.

For the "Personal" profile test, which produces no delay, before the test I exit Safari with a single window open set to "Personal". When I start Safari as part of the test, it opens with a single window set to "Personal". I do not manually open a window or switch profiles.

When I wrote "Click on the extension button and use touch id to unlock", I was referring to the button in Safari's toolbar area.

The "Trusted" profile has 5 shared tab groups. When I am running the test, I do not switch to a shared tab. The window opens in a blank, unshared tab with no content displayed. That is the what is displayed when I click on the toolbar button.

I introduced this profile right after the feature was introduced in Safari. I've never run a beta version. The delay was noticed right from the start, right after I created that profile. It's persisted ever since.

I will do more experimentation this evening. I will create a brand new profile and see if the problem exists in that profile.

In case there's any ambiguity in my description, I'd be happy to provide a screen recording of the entire flow.

I tried repeatedly to get the delay to happen while capturing in the console. I finally managed it and submitted the bug report as requested.

[#QDH-35561-584]

It's funny how it's hard to get the delay when the console is running. Sometimes I don't get the delay even without the console running, but usually I do.

I did have the Safari logging set to show timestamps. However, the exported log didn't include those timestamps. I took a screenshot of the console, which showed the timestamps, to make up for lack and included it in the bug report.

The screenshot clearly shows a 10 second timeout when requesting to unlock the accounts from the app.

[Error] Failed to request accounts in requestAndUnlockAccountsFromApp: – {type: "Timeout", content: "Timeout waiting for response to "}
(anonymous function) (background.js:2:2557472)

This bug is still killing me. It's actually gotten worse in that sometimes, even when 1Password is unlocked and the main application showing, the Safari extension stays locked. I've finally just given up working with Safari profiles; I'm now just using the Personal profile to keep 1Password working.

This bug is consistent on two different machines: a 2018 Intel running Sonoma and a 2023 M2 running Ventura. It's clearly a problem with the extension's communication with the application when running in a profile other than Personal.

One-on-one support on the issue was, as usual, excellent. However, no solution was provided. We kind of just gave up and logged the issue.

I'm interested now in two things...

Has my manifestation of the issue been reported by anyone else? Has it been duplicated by the engineers? Does it have a time frame for when I can expect a resolution?

Is there any chance the details of my configuration can be investigated further to get to the bottom of this? The problem happens in shared tabs of profiles. So both of my machines are seeing the same pages. Also, I keep 1Password configured the same way on both machines. Finally, both machines have the same Safari extensions and software running. If no one else has reported this issue, then there's something about my setup that is causing this.

Thanks Dave. Knowing that you reproduced it moves me 90% towards happiness.

No need to respond to this comment, but I just thought to add something positive in case anyone is interested.

Since disabling profiles in Safari, I've not had the issue. I unlock Safari a few times a day and I've been working with it for the last 12 days.

I don't really miss profiles.