1Password does not work with Safari profiles

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

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.

@grovolis21

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

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

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.

Do like the rest of us - switch.

@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

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?

@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