Unable to see source editor extension commands in Xcode 16

Question

Created Mar ’25

Replies 4

Boosts 1

Participants 2

I am trying to create a source editor extension in Xcode 16, I just created a blank macOS project and added an extension target. I also changed "XcodeKit.framework" to Embed and sign, but when I run the extension on my Mac, I can't see the command under "Editor" menu.

I even tried to clone a sample extension from online and run it, even in this project I'm unable to see the commands under "Editor" menu.

Has anyone faced this issue?

Answered by DTS Engineer in 829040022

Geting Xcode to recognise your source editor extension can be tricky. There are two cases to consider:

Debugging
Production

I recommend you start with the debugging case. When you create a new source editor extension target, Xcode create a scheme for it. That scheme isn’t very useful out of the box. Do this:

Use your primary copy of Xcode for this work. Ideally it’d be the one in the Applications folder.
Select the extension scheme in Product > Scheme.
Choose Product > Scheme > Edit Scheme.
In the Run action, switch to the Info tab.
On the Executable popup, choose Other and select your primary copy of Xcode.
Make sure Debug Executable is not checked.
Close the sheet and then choose Product > Run.
Xcode should launch a second copy of itself. In the Dock, you’ll see the icon with an orangey tint. Bring that to the front.
In this copy, open a test project and navigate to a source file. Your extension should be visible at the bottom of the Editor menu.

I just tried this today (Xcode 16.2 on macOS 15.3.1) and it worked a treat. I use the macOS > App template for the container app project and the macOS > Xcode Source Editor Extension template for my extension target. Oh, and as you noted, I had to change the XcodeKit setting to Embed & Sign.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’25

Recommended

Geting Xcode to recognise your source editor extension can be tricky. There are two cases to consider:

Debugging
Production

I recommend you start with the debugging case. When you create a new source editor extension target, Xcode create a scheme for it. That scheme isn’t very useful out of the box. Do this:

Use your primary copy of Xcode for this work. Ideally it’d be the one in the Applications folder.
Select the extension scheme in Product > Scheme.
Choose Product > Scheme > Edit Scheme.
In the Run action, switch to the Info tab.
On the Executable popup, choose Other and select your primary copy of Xcode.
Make sure Debug Executable is not checked.
Close the sheet and then choose Product > Run.
Xcode should launch a second copy of itself. In the Dock, you’ll see the icon with an orangey tint. Bring that to the front.
In this copy, open a test project and navigate to a source file. Your extension should be visible at the bottom of the Editor menu.

I just tried this today (Xcode 16.2 on macOS 15.3.1) and it worked a treat. I use the macOS > App template for the container app project and the macOS > Xcode Source Editor Extension template for my extension target. Oh, and as you noted, I had to change the XcodeKit setting to Embed & Sign.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

karthikk9828 OP

Mar ’25

Unfortunately this does not work. I still am not able to see the extension in the orange debuggable instance of xcode.

Xcode 16.0 macOS 15.3.2

1

Answer 3

karthikk9828 OP

Mar ’25

Is there any update in this?

0

Answer 4

karthikk9828 OP

Mar ’25

I was finally able to see the extension commands after setting up "Development Signing" instead of "Run Locally". It is documented absolutely nowhere just like how I had to change the XcodeKit.framework to Embed without signing.

0