1Password does not work with Safari profiles
Comments
-
Elsewhere others have posted the problems they are having with the 1password for safari extension not filling in, not unlocking, and basically not being useful. I am having similar problems.
Are there any updates?
1Password Version: 8.10.28
Extension Version: 2.21.0
OS Version: MacOs 14.4.1
Browser: Safari0 -
I'm sorry that you're also running into problems. Would you mind sending me a console log the next time that the issue occurs? This will allow me to determine which issue you're running into (there are a couple that our developers are looking into) and provide you with a workaround or more specific information:
Attach the file to an email message addressed to
support+forum@1password.com
.With your email please include:
- A link to this thread: https://1password.community/discussion/comment/707797/#Comment_707797
- Your forum username: kadso
- Please do not post the console log to the forum. This is for your privacy and security.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
-Dave
0 -
I am having the same issue and it has been an issue for weeks. I even reinstalled the extension for Safari.
I will send an email to the above address with reference to this thread.
0 -
Hey @jklinephd, I'm sorry for the trouble. We look forward to getting in contact with you via email.
-Evon
0 -
Same issue...
1Password Version: 8.10.28 81028034
OS Version: macOS 14.4.1
Browser: Safari0 -
Have been having this exact issue at least a month. Disabling/enabling Safari Extension works but has to be done several times a day.
0 -
I'm sorry that you're seeing the same issue when using 1Password in multiple Safari profiles. The next time that the issue occurs, please use the instructions in my post above to send in a console log and the support team can advise further for your specific situation. 🙂
-Dave
0 -
I have exactly the same issue. I have already sent console logs to you (LJU-87479-255)
0 -
Thank you for posting the Support ID. I see that my colleagues have already sent you a few emails and they'll send you another email with further steps soon. Please continue the conversation there.
-Dave
ref: LJU-87479-255
1 -
Adding another user to this. I use one profile for personal things and one for work things, as I think most people do, and 1Password doesn't work. I'm fine with the workaround for now but it really diminishes the value and user-experience of 1Password vs. Safari Passwords and other password managers that you can't use Touch ID or other unlock options.
0 -
Yes, this has been a long going issue and really impacts the ease of use. The work-around works for now but would be nice to have this resolved asap.
0 -
I too have ben having this issue with 1Password and profiles for a while. It's a big issue. Has there been any progress in resolving the issue? Is there a temporary workaround?
1Password for Mac: 8.10.33
Browser: Safari
OS: macOS Sonoma Version 14.50 -
THIS is why 1Password has been horrible in Safari all these months while working flawlessly in Chrome and Firefox? Please come up with a fix for this. For now I've decided to stop using Profiles because I need the functionality of 1P.
0 -
@clako I work in a cross-platform environment, and even though the Apple password management app will be available online via iCloud.com, 1P integrates pretty seamlessly in a mixed environment, so I plan to continue using it.
As an aside, when iOS or macOS prompts me to save a Password in the keychain, I still do it, even if I also have it in 1P. I treat it like an insurance policy.
0 -
I will add to my previous statements. 1Password seems to sort of be working in safari on my Mac OS, intermittently. For example to respond to this thread, I went to the login page, clicked on the 1P icon in the username field. 1P prompted me to unlock 1P (finger print on my Macbook), and it filled in the login info. Other times over the past few weeks 1P will fail to unlock, or a "Reload" button will popup in the Safari Extension. Sometimes it will not correctly fill in a password and I have to copy and paste (the URL is correct so it should do so).
It feels like it is more stable and getting better, but inconsistent. I don't have time to figure out when it works and when it doesn't and under what circumstances. I also don't think it matters what profile I am in as it seems to work across all of them, or not work depending on the situation.
0 -
Hello everyone,
Our developers are aware of some issues surrounding 1Password and Safari profiles and are working to improve the experience. I've made sure that all of your reports have been added to our internal work item for the issue.
For the time being, if you do run into the issue then turning the extension off and then back on should get things back to the working state:
- Open Safari, then click Safari next to the in the menu bar.
- Click Settings > Extensions.
- Turn "1Password for Safari" off and then back on.
Alternatively, if you continue to see the issue appear when using profiles in Safari, you can try one of the following workarounds:
Workaround 1: Turn off app integration
Turning off app integration will provide you with a much more stable 1Password experience when using profiles in Safari. However, with app integration turned off, you'll need to unlock the extension separately in each profile using your account password. Follow these steps in each of your Safari profiles:
- Open your Safari profile.
- Right-click on the 1Password icon in your browser's toolbar and click Settings.
- Turn off "Integrate this extension with the 1Password desktop app".
- Click Security and choose how often you'd like to be prompted to unlock 1Password in that profile.
- Repeat for each of your profiles.
Workaround 2: Use Universal Autofill to fill your logins
Instead of using the 1Password for Safari browser extension to fill logins, you can use Universal AutoFill instead. Follow these steps:
- Make sure that the 1Password for Mac desktop app is installed: Get the 1Password apps
- Setup Universal Autofill: Use Universal Autofill in apps and browsers on your Mac
- Use the
Command-Backslash
keyboard shortcut to fill logins in any of your Safari profiles.
I'm sorry again for the inconvenience. Hopefully the experience with Safari profiles is improved in a future update soon. For the time being, I hope that these suggestions help. 🙂
-Dave
ref: dev/core/core#24280
0 -
I've recently started working with multiple profiles in Safari and the experience is really bad. I have to quit Safari multiple times during the day so that the extension keeps working.
Safari profiles have been out for months now. I am not sure why or how but this needs to be fixed. Having to use universal autofill is not a workaround either, same with the workarounds above (Sorry Dave).
0 -
I'm sorry for the trouble @grovolis21 I've mentioned your report of this to the team. Thank you for letting us know you tried the workarounds. We appreciate you giving them a try.
1 -
Thanks for replying @ag_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.
0 -
I'm sorry there is no estimate available. The team is investigating.
0 -
@ag_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...
2 -
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.
0 -
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 @Dave_1P 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.
0 -
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-402552741 -
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/250750