Distributing editor extension

tl;dr: how do I distribute an Xcode editor extension with Gatekeeper?


I have written a small Xcode editor extension (and trivial containing app) and tested it locally. Now I'm trying to run it on another machine. The new Xcode docs show how to run an editor extension locally in the test version of Xcode (with the grayed-out icon), but not how to distribute it.


I took the easy route of creating an archive and exporting with Developer distribution in the Organizer. This allows me to run the containing app on a Gatekeeper-only machine. However, Xcode on this machine does not pick up the editor extension and add it to the Editor menu.


I don't know if the problem is that Xcode doesn't know to look for the extension inside of apps in /Applications, does not pick it up from the host app running, or if it knows the extension is there but doesn't like how it's signed, etc. It certainly looked like the Organizer signed both the app and the extension (see screenshot here).


I realize there are a wide number of complex and horrifying techniques I could employ from TN2206, macOS Code Signing in Depth, such as creating a DMG and then signing it with codesign on the command-line. I'm not inclined to dig into these approaches until and unless I know that just using the Organizer is not sufficient.


Thanks in advance.


—Chris

Answered by invalidname in 281972022

Never mind, I'm a *******. I'd overlooked that extensions need to be explicitly enabled via System Preferences > Extensions > XCode Source Editor.

Accepted Answer

Never mind, I'm a *******. I'd overlooked that extensions need to be explicitly enabled via System Preferences > Extensions > XCode Source Editor.

Distributing editor extension
 
 
Q