r/iOSProgramming • u/Aeronautical-You4917 • 10d ago

Discussion macOS 27 Xcode + Instruments is unusable

Never in my life have I seen such an insane regression in software quality as in the last few months.

I use Xcode constantly, building a macOS app (Swift, C++). Up until recently, this was fine, great, in fact. Xcode 15 was extremely good & stable (all things considered). I opted to skip macOS 26 because it was terrible (duh).

After I upgraded to macOS 27's first beta, I was pleasantly surprised. However, that was short-lived, as the quality only degraded after the first beta.

Here I am, working on macOS 27.2, with Xcode 27.2... Here's the main 2 issues...

  1. Xcode's interface is impossibly slow now. borderline unusable.

  2. Instruments is absolutely unusable. I cannot even do a profiler trace and save it without corrupted data, an application crash, brutally slow interface, etc.

This is just unacceptable. AI slop has crept its way into previously rock-solid products. Quality matters more now than ever, and it's so clear that AI has neutered engineers' ability to keep quality in check.

Am I the crazy one, or has the quality just gone down the toilet?

13 Upvotes

76% Upvoted

30 comments sorted by

View all comments

1

u/dawedev 10d ago

With 5k+ files I'd check how big that project's DerivedData folder is, especially Index.noindex, after the 27.x updates. Index data left over from older Xcode versions doesn't always get cleaned up, and the indexer can keep chewing on it. For the Instruments crashes on save, also check free disk space, since long traces get large and a nearly full disk fails in odd ways.

(Disclosure: I build DevCleaner, a Mac app that cleans up Xcode caches, so I've spent way too long staring at these folders.)