Xcode 26.0.1 keeps crashing, freezing, and losing UI connections on small projects (Assistant Editor arrows crash, storyboard drag causes beachball, outlet/IBAction circles disappear) on macOS 26.0

austinwellsdev wrote:

I’m running Xcode 26.0.1 (build 24229) on macOS 26.0 (25A354) with a MacBook Pro Apple M4 Pro chip and 48GB of memory. I’m not working on large projects, yet Xcode has been very unstable for me.

Most recently, Xcode quit unexpectedly when I clicked the navigation arrow in the Assistant Editor. The crash report shows an EXC_BAD_ACCESS (SIGSEGV)• in AppKit when handling selection changes via NSControllerConfigurationBinder. The crash stack points to Cocoa bindings being triggered by the Assistant Editor’s selection navigation.

This is just the latest in a string of issues:

Xcode often runs slow or freezes. For example, when dragging a UI element onto the storyboard, the IDE beachballs (spinning rainbow cursor), then eventually “catches up.”

• If I add new lines near an @IBAction or @IBOutlet, the circle connection indicators in the gutter vanish. They only reappear if I completely close and reopen Xcode.

• etc. etc...

I’m not working on large or complex projects, it feels like this is an IDE stability/performance issue rather than a resource problem. Has anyone else run into similar issues with the Assistant Editor crash, storyboard freezes, or disappearing connection indicators on Xcode 26?

austinwellsdev wrote:

if you cp them from ~/Library/Logs/DiagnosticReports/ to your desktop or documents folder then running textutil is not destructive. Converting them to .txt format is to make it easier to have AI parse it. This is just one way to diagnose for people that don’t know how to read these reports or know what SIGSEGV means.

They already are text. They aren't designed for AI or for end users. They're designed for developers. Scrambling them like that makes them useless for their designed purpose.

And furthermore, opening these reports in Console will automatically show them in a more traditional, human-readable format.

Console has big "share" button right on the toolbar that does all you'll ever need.

austinwellsdev wrote:

I’m really not sure what you mean by ‘scrambling’…

Adulteration. Folding, spindling, mutilating, whatever.

You can see it in many EtreCheck reports here in the forums. These are text files specially constructed to be easily pasted into the forums with a single click. Yet people won't just click that button. Instead, they do all kinds of routing text through PDF, Word, etc., only to post some freakish text version back here in the forums.

You can go to console and try to read the output of your crash log, then, if you are a beginner developer and get confused, you can do whatever non-destructive task you want to figure out why your machine isn’t working.

Console is specially designed to automatically convert that IPS file into a more traditional, and more human readable, form. Those IPS files are actually designed to be routed through Apple automatically and show up in the Developer's Xcode.

But developers who don't have apps in the App Store have to manually do the symbolication themselves, from the text version that Console generates. When a user scrambles the crash report first, then Console won't be able to read it.

Your instructions aren't going to help people find bugs, they are going to prevent bugs from being fixed.

I don't know what problem you were having with Xcode. Your computer is far more powerful than any computer that I have and I regularly use very complicated projects. Xcode does sometimes crash, and Internet Builder has been neglected and infuriating for years. But you aren't going to be able to fix any of that by reading Xcode crash reports. Nor are you going to affect any change at Apple. At best, you're going to make life more difficult for some small developer having unreproducible crashes and users sending them corrupted crash reports.

OR; As beginner in coding, dump XCode Editor for the mean time? Which is used as alternative that performs better?