Safari extension not showing up

Question

DownUnderGlen OP

Created Nov ’16

Replies 7

Boosts 0

Views 6.8k

Participants 6

Hi,

I'm trying to investigate the new Safari App Extension architecture but cannot even get through this basic tutorial:

https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/ExtensionCreation.html#//apple_ref/doc/uid/TP40014214-CH5-SW1

FWIW, I'm on El Capitan 10.11.6. My Safari version is 10.0.1. I'm using Xcode 8.0. The only deviations from the tutorial are in the targets that I have defined. I created a new project based on the OSX Cocoa Application template. I then added a macOS Safari Extension template - they are both unmodified. This builds and runs as expected; an empty application window pops up.

In Safari, I then navigate to Preferences -> Extensions. The extension bundled with the app is not available in the left hand pane as directed by the tutorial.

I have got the Develop menu enabled and "Allow unsigned extensions" is checked. I suspect this is some kind of signing issue and that Xcode is ignoring my extension. Each target is "Ad Hoc Signed". FWIW - I did try adjusting Build Settings to "Don't Code Sign" for each target but see the same problem.

Anyone out there experiencing similar issues or have good advice on how to resolve this. I see nothing indicating a problem in any logs and am not sure how to go about debugging this. Any advice would be greatly appreciated!

Boost

Answer 1

DownUnderGlen OP

Nov ’16

For anybody suffering the same issue, this started working as documented after I updated everything to the latest: Xcode 8.1, Swift 10.0 (it seemed to lose the .1?!) and Sierra.

0

Answer 2

DownUnderGlen OP

Dec ’16

I suffered a further similar problem like this with Xcode 8.1 where the extension stopped showing again. Something occurred where my extension stopped being included in my containing app.

This manifested as when performing a programmatic state check on the extension:

SFErrorDomain code = 1 (NoExtensionFound).

In case, anyone else comes looking, I selected the Extension target to build and Safari as the App to run. This runs the extension standalone which is pretty cool! When I switched back to building the containing app, my extension was being included in my bundle again. Seemed like Xcode decided not to copy my extension artifacts into my app bundle for some reason.

0

Answer 3

brendanchatt OP

Dec ’20

I'm experiencing this issue as well. But mine is signed properly

0

Answer 4

M4GG1 OP

Jan ’21

I had this issue a few days ago as well, and it resolved itself after several restarts.
It worked until the next restart, where it suddenly stopped working again.
I find it very strange, because a

Code Block swiftprint(error.debugDescription)

seems to output "SFErrorDomain code = 1 (NoExtensionFound)".
This error appears to indicate, that the App couldn't access the extension / the bundle id isn't found, what is very very strange, because the extension is clearly found in "Package Contents" > "Contents" > "PlugIns" and looking at my configuration, the bundle id's are matching.
I have also checked "Allow Unsigned Extensions" in Safari.

Any news on this?

Thanks in advance! :)

0

Answer 5

Engineer OP

Apple

Jan ’21

Make sure that:

1) The deployment target for your app and extension include the version of macOS you are running
2) Each time you quit/restart Safari, go to the Develop menu and select "Allow Unsigned Extensions".

If those don't work, please collect a sysdiagnose and file feedback at https://feedbackassistant.apple.com

Thanks!

1

Answer 6

nixoloco OP

Dec ’21

I had a similar problem recently after updating to Xcode 13.2.1 and a MacOS update. My Safari webextensions in development weren't showing up any more in Safari (even with unsigned extensions enabled).

I think it turned out to be a problem with LaunchServices and Safari because running the following in a commandline/terminal fixed the problem:

PATH=/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support:"$PATH"lsregister -f /Applications/Safari.app

Then my extensions started showing up again instantly.

1

Answer 7

natesilva OP

Jul ’22

Thank you, @nixoloco. Your solution worked for me. This has been bugging me for months and this fixed it! I am not an extension developer but I have Xcode 13 installed. I don’t know how my Launch Services database got messed up.

Note: add a space before lsregister:

PATH=/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support:"$PATH" lsregister -f /Applications/Safari.app

1