nshipster.com | overlooked bits in Objective-C , Swift , and Cocoa | iOS library

I was able to figure this out thanks to the LinuxSupportForXcode extension.

I'm going to make the assumption that you followed the tutorial on creating an Xcode Extension Editor, and made the main project a macOS App. You should have a target structure similar to:

• MyApp (macOS App target)
• MyAppExtension (Xcode Source Editor Extension target)

To use XPC with a Source Editor Extension:

1. File > New > Target... > XPC Service.

   For example purposes, we'll assume it's called MyAppXPCService and its bundle identifier is com.example.MyAppXPCService.

2. Move the XPC service dependency from the App to the Extension:

   If you don't do this step, you may run into issues where your XPCService isn't being executed by the extension. E.g. you invoke a command that should launch the XPCService, but in the Xcode Debug Navigator, your XPCService never comes up.

   1. Go to your app's target.
   2. Remove MyAppXPCService.xpc from the Frameworks and Libraries.
   3. Go to your extension's target.
   4. Add MyAppXPCService.xpc to Frameworks and Libraries by dragging it in from the products folder in the Project Navigator. Leave it on the default "Embed Without Signing".

3. In the XPC Service, convert it to Swift, mainly following the instructions here:

   Note: If you'd prefer to not convert to Swift, and use a mixed target instead, simply create a Swift file and when prompted, choose to create the bridging header, then include #import "MyAppXPCServiceProtocol.h" in the bridging header.

   1. Create main.swift, MyService.swift, MyServiceDelegate.swift, MyServiceProtocol.swift normally.

   2. Set the following build settings:

      • Install Objective-C Compatibility Header: NO
      • Objective-C Generated Interface Header Name: `` (blank)

   3. Choose your desired Swift Language Version in Build Settings.

   4. In Build Settings, add (don't replace): @loader_path/../../../../Frameworks to Runtime Search Paths.

      If you accidentally replace, and use an embedded framework, XPC will crash on launch.

4. In your extension target:

   1. import MyAppXPCService so that it can see the protocol.

   2. Create the connection, using your XPC target's bundle identifier for serviceName:

Looks like the following works:

The definition says: Reflection is a common programming language feature that enables us to inspect, and work with, the members of a type — dynamically, at runtime. Members are list of properties inside a class/struct.

So, if you want to iterate over all your types that confirm Animal protocol, you need to have them as members in a type, and then iterate over it.

Check code below-:

I was able to sort this out after reading Using App Groups for communication between macOS/iOS apps from the Same Vendor

The problem was that as of Big Sur (or possibly Catalina), macOS apps using App Groups require a group container to be created in the developer portal. after doing that, you need to reconfigure the code-signing your app to include a provisioning profile. I'm not really sure when this all became a requirement since setting up App Groups isn't really well-documented by Apple. Everything works great after following the steps in the above linked article.

I was able to get my array passed from one app to another:

According to the docs:

When you include property wrapper arguments, you can also specify an initial value using assignment. Swift treats the assignment like a wrappedValue argument and uses the initializer that accepts the arguments you include.

So it translates your property declaration into something like:

As stated in the documentation,

begin by creating a new macOS project in Xcode. Add a new Xcode Source Editor Extension target to your project

In other words, first create a new project. Then create a new target in said project. That target being an Xcode Source Editor Extension.

Silly solution, though aided by @Willeke's comment that they weren't seeing an error with the same code snippet—the library needed Cocoa.h in place of the iOS imports.

I'm not aware of any trick to make the Siri voice available and I'm afraid it's impossible to make it working via public API.

• Both NSSpeechSynthesizer and AVSpeechSynthesizer do utilize SpeechSynthesis.framework (included in the ApplicationServices.framework).
• Quickly checked it and the function BuildDefaultVoiceList(bool) checks bundle identifier (via PermitAllVoices which compares it with com.apple.VoiceOverUtility, com.apple.VoiceOver, com.apple.VoiceOverUtilityCacheBuilder).
• There're other checks probably.

All the voices are stored in the /System/Library/Speech/Voices folder. Tried to copy the voice, change Info.plist values to make it look like another voice, but still not available/working.

How far do you want to go? Do you want to disable SIP, modify framework, preload your stuff, ... Is it worth it?

It works, but it's buggy and you have to kill the service from time to time.

I just received feedback from Apple about this. The documentation is currently well hidden in the header file NSOperation.h. Here is the extract for anybody who encounters the same problem: