Xcode 26.0.1
Xcode 26.0.1 requires a Mac running macOS Sequoia 15.6 or later.
[…]
Fixed: Icon Composer documents that use “Lighten”, “Darken” or “Screen” blend modes incorrectly encode as “Normal” when compiled. Blend modes will look correct in Icon Composer, but not at runtime.
I don’t think this was affecting my icons, but I’ve seen a bunch of developers and designers distressed that their icons were not looking the same in the Dock as in Icon Composer.
Previously:
Update (2025-09-26): Avi Drissman:
I’m seeing Icon Composer not matching the Finder with Combined mode, and that’s not fixed in 26.0.1. Hopeful now that a different display bug was fixed.
If you used the Xcode 26 betas, make sure to go into Xcode settings and clean out the iOS 26.0 beta simulators that you no longer need. Mine didn’t get deleted automatically and each one consumed about 10 GB. 😳
Update (2025-09-29): Marcin Krzyzanowski:
I WANT TO SCREAM. Apparently #Xcode 26.0.1 has problems building Metal on macOS 26, too!
The year is 2045, robots walk among us, but connecting a new device to Xcode still prevents you from being able to do any work until it’s finished.
I could find absolutely no option anywhere that would make my existing (~7 years old) app project use the IconComposer.icon file in preference to the XSCAsset. In the end I just recreated the project from scratch, which worked.
I can’t meaningfully diff the project files, so I guess it will forever remain a mystery why it didn’t work before.
Update (2025-09-30): Pol Piella Abadia:
As of Xcode 26, the Metal toolchain is no longer included in Xcode’s installation by default. This means that, if your app or one of your dependencies needs to use the toolchain, you will need to install it manually before building your app.
[…]
However, if you happen to be using a CI/CD runner that is not provisioned with the Metal toolchain installed, you will get the same error as above, but this time, you will likely not have access to Xcode to be able to install the toolchain.
You might be surprised to learn that this is the case for Xcode Cloud, as I recently discovered the hard way when migrating my CI/CD workflows to use Xcode 26.
When WWDC happened, I remember thinking to myself, “Finally, Xcode tabs will make sense”.
I’m not sure what happened — nor if it’s a me-problem or an Xcode-problem — but they continue to not make any goddamn sense to me.
Update (2025-10-17): Steve Troughton-Smith:
Not something I’ve seen before — Xcode 26 has a hotfix you can install inside the Components settings pane that will add new device support to the Simulator, without downloading a new version of Xcode.
Update (2025-10-29): Pedro Piñera:
Don’t engineers at @Apple experience this beauty of UI that reacts to state? If so, I have many question about how they operate internally such that not a single engineer has fixed this experience[…]
