The app is pretty much unusable with Safari if you use profiles. Sometimes it won't unlock, sometimes it will only unlock with the icon in the browser bar, sometimes it will unlock but nothing will fill. It may work in one profile, and fail in others. Much of the time I have to open the 1Password app, search it for the site I'm on, and copy and paste the password into Safari. It works fine in other browsers. 1Password Version: 8.10.27 Extension Version: 2.21.0 OS Version: macOS 14.4 Browser: Safari

I switched back to Safari expressly because they (finally) introduced profiles, but I'm having the same problem as most of the posters above. I will start to collect the data you cited above and submit it for your review, but from an end-user point of view I can just say that the experience is very frustrating. For me, in most profiles, 1Password has turned from a fully-functional easy-to-use tool to one that merely remembers passwords, but I have to manually cut/paste them (let alone any of the other functionality). I suggest you also do some internal testing, as I (for one) did nothing particularly special to engender the problem, other than to enable several profiles.

Hey steph_giles , I have regularly the same problem as described above. I looked at the logs of the extension, but they stay empty. When clicking on the extension icon, I get a button "Open 1Password" that does nothing. The 1Password app is unlocked. I found out today another workaround then quitting Safari. If I manually lock the 1Password app and unlock again, then suddenly the safari extension is working again. It seems to be a communication problem between the extension and the backend. Have you been able to reproduce internally? On a side note: this behaviour is quite annoying as it makes using 1Password anything but a smooth experience like it used to be. I do not recall permanently recurring problems as this one with 1Password 7. Since 1Password 8, it feels that 1Password is constantly getting in the way. Regards, Stan.

Got it again Safari with two profiles open. Left the machine so screensaver went on. Unlocked the machine Opened a new window with a new profile. Clicked on the icon by the entry field The app popped up and I entered the password. Then nothing in safari Clicked on the icon by the entry field - nothing. Clicked on the icon in the bar. Got a popup saying open 1password and nothing else (Why 1password is open) Hitting the open 1password button does nothing Click on the app in the dock - yes it is open Close the safari window an open and the same. This is so repeatable - it does this or it does a slow load of the popup from the web bar button. Every single time. The popup button does show all the logins in the profile I am writing this in. Just not in another profile.

1P_Tommy Has the "investigation" found anything? This has been going on for way too long and it is unacceptable for a paid product. It's coming up on 8 months since the issue started...

I'm using the Safari 1Password extension with profiles. The extension is enabled globally on all profiles. If I unlock the password extension on one profile, the extension stays locked on the other profiles and seems confused about the lock status. I can click on the icon in the toolbar (which shows it is locked), but all I get is "Open 1Password" to kick me out to the app. Unfortunately, that doesn't work. Autofill capabilities also do not work on the other profile. 1Password Version: 8.10.18 (81018040) Extension Version: 2.17.0 OS Version: macOS 14.1 Browser: Safari

1Password does not work with Safari profiles

EggsAndAvo
Contributor
4 months ago
Also an issue for me still, ridiculous that it's been over a year.
clako
New Contributor
4 months ago
Do like the rest of us - switch.
kzolnowski
Occasional Contributor
4 months ago
1P_Dave I'm on 8.10.52.25 now and this is still an issue for me.
1P_Dave
Moderator
6 months ago
billimek

Our developers have released improvements to how 1Password communicates with Safari profiles in the latest versions of 1Password for Safari. Please update to 8.10.46 and let me know if you still run into issue:

How to keep 1Password up to date in your browser

There are still a few cases where profiles are putting up a challenge and the team is investigating. If you run into one of those cases with 8.10.46 then let me know and I'll get that report to the team.

-Dave

ref: dev/core/core#28250
ref: core/core/-/merge_requests/25075
billimek
New Contributor
6 months ago
Hi 1P_Dave, it's been a while since your last post about this. Can you share if the possible fix has been introduced into a beta version yet?
1P_Dave
Moderator
7 months ago
rzei

I'm sorry for the continued inconvenience. Our developers believe that they have identified the cause of the issue and are coding a fix that should improve the situation with Safari profiles. I hope that a fix will be released to the beta and then the stable version soon but I don't have a release date to provide at the moment.

I see that my colleague has already passed along your feedback to the product team via the support ticket that you mentioned. Thanks again for that feedback. 🙂

-Dave

ref: dev/core/core#24280
ref: PB-40255274
clako
New Contributor
7 months ago
Do like the rest of us - switch.
rzei
New Contributor
7 months ago
Still the same issue here. I have already previously communicated with support (RJH-48459-724) resulting in the same suggestions of trying Workaround 1 or 2, both of which work but severely degrade functionality.

So I would like to reiterate that the current state of the Safari extension is really not acceptable and needs to be fixed. I'd also like to point out that in another thread the following reason was given by 1P_Dave for not implementing the native MacOS Credential Provider API:

In addition, 1Password in the browser and Universal Autofill are developed by our team and that means that 1Password can directly fix filling issues when they occur, something that wouldn't be possible with macOS AutoFill.
Clearly this hasn't happened and, on the contrary, I would think that the native API would generally be more stable (as evidenced by other third-party apps such as Strongbox that implement this functionality).

Having said all that, I've found the following variant of Workaround 1 which, while still not ideal, has reduced friction for me a little bit: Instead of disabling application integration in all Safari profiles, it seems sufficient to disable it in all but one. That way, I can keep app integration including biometric unlocking in my most used profile.
1P_Tommy
Moderator
8 months ago
I am not aware of any change. It's possible several things have been tried and then shelved having not produced acceptable results. It's possible we've submitted this to Apple as a bug that we need help resolving to move forward. I've seen no indication of that but I am not a developer. A myriad of possibilities exist. I'm sorry a resolution has not been available to you.

The good thing is you have other browser options available and drag and drop is a possibility. Universal Auto-fill is another suggestion you might use.
EggsAndAvo
Contributor
8 months ago
1P_Tommy Has the "investigation" found anything? This has been going on for way too long and it is unacceptable for a paid product. It's coming up on 8 months since the issue started...