Skip to main content
Mar 15, 2024 12:12 PM UTC
Solved

1Password does not work with Safari profiles

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

1P_Dave
1P_DaveAnswer
1Password Employee
Mar 14, 2025 7:23 PM UTC

Hello folks! 

Our developers have released improvements to how 1Password communicates with Safari profiles in the latest versions of 1Password for Safari. Please make sure that you're running the latest versions of both macOS and 1Password for Safari: 


If you're still seeing issues with the latest version of 1Password for Safari and macOS then I'd like to ask you to create a new diagnostics report from 1Password in your browser so that the team can identify whether you're running into a known issue and help further:

Send a diagnostics report (browser extension)

Attach the diagnostics to an email message addressed to support@1password.com

With your email please include:

  • A link to this thread: https://www.1password.community/discussions/1password/1password-does-not-work-with-safari-profiles/92139?topicRepliesSort=postTimeDesc
  • Your forum username: username


You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here.  Thanks very much!

-Dave

70 replies

Jun 19, 2024 11:43 AM UTC

I've actually gotten to the point that I've begun relying entirely on the 'built-in' Safari password manager. It's sad, but it works and does the job for me

grovolis21
Jun 19, 2024 5:41 PM UTC

Thanks for replying @1P_Tommy, is there any timeline or news regarding this issue?

The locked 1Password extension on one of the profiles in the screenshot below is what I was describing in my reply above.

1P_Tommy
1Password Employee
1Password Employee
Jun 19, 2024 7:04 PM UTC

@grovolis21

I'm sorry there is no estimate available. The team is investigating.

Jul 17, 2024 10:57 AM UTC

@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...

1P_Tommy
1Password Employee
1Password Employee
Jul 17, 2024 12:18 PM UTC

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.

Aug 17, 2024 10:18 AM UTC

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 https://1password.community/discussion/comment/708916 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.

Aug 17, 2024 11:23 AM UTC

Do like the rest of us - switch.

1P_Dave
1Password Employee
1Password Employee
Aug 19, 2024 3:49 PM UTC

@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

billimek
Sep 30, 2024 1:30 PM UTC

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
1Password Employee
1Password Employee
Oct 1, 2024 2:07 PM UTC

@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:

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