Copy your Xcode14.2.app 's xcs files to Xcode 14.3 and replace. Any stable xcs and replace the new Xcode cp -r /Applications/Xcode-14.2.0.app/Contents/Developer/usr/share/xcs /Applications/Xcode.app/Contents/Developer/usr/share

Add new error log from xcs by console. XCSBuilderServerFaile2.log

add New console log. `Unexpected type 4 for interface index 1 from libnetcore event EventDescription sb at 0x14372f050 from pid 25062 XCSBuilderServi SYMPTOM 0x6767005 flags 0x40000003 qual0 0x1 qual1 0x61e6 key 421893 num additional quals 3

flow this doc: Xcode Server and Continuous Integration Guide

DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. fix them use. https://stackoverflow.com/questions/52165333/deprecationwarning-buffer-is-deprecated-due-to-security-and-usability-issues replace at this path code of JS /Applications/Xcode.app/Contents/Developer/usr/share/xcs

The thing that caught our eye is the UIKit module error, with a file path pointing to the build folder for your app, and this is where we’d like to focus first. I was hoping we’d see some correlating evidence of what’s happening here through the build log, but there wasn’t anything in the build log to assist. The next thing you should do is run the Swift health check LLDB command to assess any issues with the modules referred to by your app. We discuss this command in the following WWDC video: https://developer.apple.com/videos/play/wwdc2022/110370/

Here is my crash info. . Thanks your support. 2022-09-14_13-26-48.1330_+0700-470e222fa3ea71fc29751f9f4b0817e74f4da2ff.crash

New Version Xcode was fixed.

I have solved this problem. This is a bug. The bug from macOS 12. Why I am saying this? I tried to wipe all the disks and reinstall macOS 12.2, then install Xcode, start Xcode Server, crash on the same error. Finally, in retrospect, my M1 computer was upgraded from macOS 11, and when it was activated on macOS 11, due to misoperation. This resulted in the need to execute the 'xcscontrol —reset' command in macOS 12. So the reason for this problem is the reason for the system. Last night, the same use of erasing disks, installing macOS 11.6, then installing Xcode all came back together. In the coming year, I don't plan to upgrade to the latest system. I feedback this bug to Apple, hoping that someone can solve this problem quickly.

Do you have reinstalled macOS?

I was sent the feedback by Feedback Assistant.