XPC | XPC and Friends | iOS library

I upgraded from XCode 12.5.0 to 13.2.1 and the problem is resolved. It seems to have been an SDK mismatch and therefore the XPC messages were not being deserialized properly.

It would be good to get a more robust answer of how XPC messages work but I have not found a lot of resources on that. In lieu of that I can at least say this has solved the problem.

Two applications by themselves cannot directly talk to one another via XPC. If you need to securely share memory between two applications on macOS, XPC likely is your best option - it will just involve some additional setup.

The core concept to understand here is that there are only two ways to establish an XPC connection:

1. Connecting to a named service managed by launchd.
2. Connecting to an XPC endpoint. However, the only way for a process to get access to an XPC endpoint that is associated with a listener connection in another service is over another XPC connection.

The reason you can't have one GUI application directly connection to another over XPC is neither of your GUI applications are going to be managed by launchd. And if you're wondering, well can my GUI application be managed by launchd? The answer is no; launchd only manages services (which are dynamically started and can be terminated if system resources are needed).

The way you'll need to do this is:

1. Create a Launch Agent. (Theoretically you could instead create a Launch Daemon, but there's no good reason to — you don't need root permission for what you're trying to do.)
2. Have your Launch Agent vend a XPC Mach service. (This corresponds with #1 above when I was describing the core concept.)
3. Have one of your GUI applications create an anonymous listener connection. Then get that listener's endpoint.
4. Have that GUI application send your Launch Agent its endpoint.
5. Have your other GUI application ask your Launch Agent for the endpoint.
6. Have the other GUI application create a connection using that endpoint.

At this point your two GUI applications can directly talk to one another.

What I described is a bit oversimplified. For example you may way to have a design where both of them create an anonymous listener connection, send it to the Launch Agent, and if one already exists from the other application then it can return that. To avoid race conditions inside the Launch Agent you can DispatchQueue to serialize its processing of requests from the GUI applications.

FYI I linked to the Objective-C versions of the API because your post tagged nsxpcconnection. However, there are also C API equivalents for all of this. If you have a cross-platform codebase, you may find the C API much easier to integrate.

It does not duplicate the Timer it creates a new Class instance with a new Timer, you can try and use a singleton for the beginning - forcing only one instance of the class. A long-run solution will be to use some Dependency Injection solution to control the class lifecycle

There is a protocol which your extension's principal class can implement, NSFileProviderServicing.

https://developer.apple.com/documentation/fileprovider/nsfileproviderservicing

So I could not fing the error, but I managed to make workaround. I added folloowing code to my func openSharingService(), in order to recognize Add to Photos and handle it in a different way:

Here's one way to do this in zsh and bash:

While your print statement is outputting XML that, if reparsed, would give you the correct result, your in-memory DOM doesn't have awareness of the namespace of the new element. To tell the new element about the namespaces, we can use SetNamespace and SetAttributeNS per the docs

Following code sample demonstrates how you could use %hash for alternation you try to achieve.

Problem solved by a colleague, turned out a few providers (DatePipe, Location, Market, InAppBrowser) in app.component.ts and a router animation were causing the fuss.