[client] No error handler for XPC error: Connection invalid

Question

Created Feb ’23

Replies 4

Boosts 3

Views 5.7k

Participants 5

Hello everyone, With the MacOS update to Venture 13.2, I get the following error message when closing a MacOS app in xCode: [client] No error handler for XPC error: Connection invalid Today I set up a brand new MacOS system which has nothing more installed as except for MacOS Venture 13.2 and xCode 14.2 (14C18). The error already occurs when I start an app that only contains template code. I also started the app without xCode and then closed it through the menu. Then I do not receive an error message. With the Ventura version 13.1 on an AirBook with M1, the problem did not exist. On my Intel iMac, the error causes the iMac to no longer start normally. Thank you very much for your support.

Boost

Answer 1

DTS Engineer OP

Apple

Feb ’23

The error already occurs when I start an app that only contains template code.

So, lemme see if I understand this properly:

You create a new project from the Xcode macOS > App template.
You run that.
You quit it using File > Quit.
You see this log message.

Is that correct?

If so, that’s definitely log noise. See On Log Noise for my advice on that front.

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

0

Answer 2

jeanlain OP

May ’23

I'm getting the same message when I quit my App during a debug session. That started occurring after some macOS/Xcode update.

This message isn't associated with any issue and I confirm that it is posted even when quitting a bare-bones template Mac app.

0

Answer 3

raldrich OP

May ’23

I've seen this in my application as well - According to Activity monitor the XPC service in question is most likely the "Open and Save Panel service".

0

Answer 4

haroldfromdearborn OP

Oct ’23

Thanks for the comment about Log Noise. I recently was able to identify a dangling menu item action in Main after an update that let me see the action instead of naming it "private". This is the only error message I have been able to use after years of coding. Otherwise I test, ignore and wait for somebody to clean it up. Keep up the good work. Thanks for giving it a name.

1