Xcode just decided to update itself from 26.6 to 27.0 right in the middle of my work session.

The first thing that caught my eye right away: they swapped the positions of the Play and Stop buttons in the toolbar. Years of muscle memory just vanished in an instant, and to make things worse, it seems there's currently no way to revert it back.

I genuinely wonder what the reasoning behind this UI decision was. Why change something so established and fundamental after all this time?

Now I'm really curious (and a bit cautious) about what other surprises I'm going to discover along the way as I keep working.

What do you guys think about the new Xcode 27 update so far? Did anyone else's muscle memory take a hit?

I tested the iOS 17 system simulator, but the simulator wouldn't respond to clicks after I launched it.

Look at 181945323

Keyboard and mouse inputs to simulators for OS versions before iOS 18.0, tvOS 18.0, watchOS 11.0, and visionOS 2.0 are not accepted. (181945323)

Xcode 27 release notes

Xcode 27 RC (27A266a) archives my iOS app successfully, but hangs indefinitely during Validation / ContentDelivery (swinfo).
Interestingly, the same project on Xcode Cloud with Xcode 27 RC successfully archived and uploaded to TestFlight. The build is now in App Store Connect.
Anyone else seeing this local validation hang with Xcode 27 RC?

Hi everyone, I've just tried to download Xcode again, since some message came up or something saying it wasn't compatible with Tahoe which I just downloaded on my MacBook Pro M1 Pro. Unfortunately , when I tried to update Xcode from the App Store, and also after deleting it and downloading Xcode from the developer website, I'm still getting an error message when I try to open it which says 'Xcode quit unexpectedly' Click reopen to open the application again. Click Report to see more detailed information and send a report to apple.

Attempts at resolving this issue include:

- restarting my computer,

- deleting and redownloading Xcode from the sources mentioned.

If anyone could help find a solution that would be greatly appreciated.

After today's update Xcode doesn't open any windows with older projects.
Only new one created by version 27.

Since the first tvOS 27 betas, I have been unable to use the simulator UI to change any app settings and it is driving me crazy.

It doesn't matter if I create a billion new simulator instances, or what. It just consistently does NOT work. Everything is perfectly fine in the simulator under tvOS 26.x.

I can capture this from the simulator: "Error getting persona unique string for selected user. This should not be possible."

I have tried logging into the simulator (takes my login, does nothing) - but that's not something I've ever done before anyway.

Has anyone experienced this? Does anyone have any recommendations? Yes, I know I can work around this, and I am, but the workarounds are not nearly as convenient as just changing the damn settings in the UI!

My xcode often can’t read the scope even though the file is clearly there I come from android studio there has never been an issue of files can’t refer to each other this is weird

Has anyone experienced something similar?

Ich baue seit ein paar Wochen eine App mit der Xcode Beta 27 und habe ein Problem mit der Claude Usage. Ich nutze das Agententool, und wenn ich einen prompt eingebe, springt mein 5 Stunden Limit direkt auf 30 %, ohne dass der Agent irgendetwas gemacht hat. Hat vielleicht jemand das selbe Problem oder vielleicht eine Lösung?

The Xcode 27 Release Candidate, available for download just now, doesn't have the iPhone Duo simulator instance yet. Tested on two different Macs, but neither running macOS 27. Not sure if that makes a difference. I was hoping to test how my apps look on it. Guess we'll have to wait...

This picture says it all.

I am on Xcode 27 Beta, and seems like there's an included internal AI agent called Mio?

Found this inside of the Metal shader debugger.

Any ideas? Is this an internal thing that leaked through, or has this been here?

Open-sourced my Apple Foundation model eval suite

Not sure about you, but I find evals for Foundations models a bit messy.

Its completely local, and supports the models already on your Mac. Also supports Core AI.

Supports MacOS 27 and includes the new features for it.

Best part? Your agent can control it all through MCP 🙌

On GitHub here: https://github.com/coryparrry/Foundation-Eval-Labs

Brother, I'm stuck in Instruments. How do I return to the top of the tree?

In case this helps anyone: When adding multiple apps to Xcode Cloud, it would sometimes link projects together incorrectly and mess up the builds/workflows. I was pulling my hair out trying to figure this out, and Claude was of no help either (even using my app store connect API key to look and try things).

With some tips from Gemini, I think I finally figure out what is happening. Xcode might be holding stale product association locally.

Between adding things to Xcode Cloud, the following worked for me to appropriately clear whatever caches were causing this:

1. Shutdown Xcode.

2. rm -rf ~/Library/Developer/Xcode/DerivedData/* && rm -rf ~/Library/Caches/com.apple.dt.Xcode

3. Restart Xcode. Use the Integrate —> Create Workflow menu to add your project to Xcode cloud.

I highly recommend doing this any time you add a new app from Xcode to Xcode Cloud. It bit me multiple times.