Cannot install Safari extension

Hey @joshuacale and @avery_shealey:

Glad to hear that worked for you. As mentioned in the link @klanchman posted, this doesn't appear to be specific to 1Password. We've reported this issue to Apple for further investigation, but for now, our best recommendation is the terminal command as needed. Thanks for your patience on this!

Jack

I encountered the same issue - extension disappeared for seemingly no reason overnight and I could not get it to appear again in the extensions menu of safari preferences. Running the terminal command above solved the problem.

Fixed for me as well. I removed the app and reinstalled several times (both 1Password and 1Password for Safari). Agilebits may want to look into why removing/reinstalling isn't fixing the issue by itself - it shouldn't take doing that in the terminal to unblock enabling the extension. Thanks klachman.

Great to hear @gompy! :smile:

Thanx, fixed it for me also!

Thanks for chiming in @klanchman! Glad to hear the terminal command helped with registering 1Password in Safari for you again. :+1:

I ran into this today. I already had the extension and had been using it without issue, but it seemingly disappeared overnight. Quitting Safari, reinstalling the extension, and rebooting the computer all did not help.

I remembered reading something similar a little while ago and dug it up: https://lapcatsoftware.com/articles/disappearing-safari.html

I ran this in Terminal.app, as the article suggested:


/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -f -R /Applications/Safari.app


and it fixed the issue for me! Hopefully this helps anyone else who starts seeing this problem :smile:

Great to hear things are working again for you @JohnnyFJohnsson! :smile:

Hi @ag_ana, I have reinstalled MacOS as somehow also my iCloud Drive was not fetching any files so something must have messed with my configuration. Now the Safari browser extension works again. Thanks for your help even if the error was on my side.

@ag_ana unfortunately I do not see it in in the Safari Preferences.