The way to see all environment variable values is to add a run script to your build phases.

Bump. I repeat the question. Xcode 13 is final. I need the Vary For Traits feature. Some of my apps use it. Where is it?

The rule you are breaking is that capitalization matters when you spell a name. You're saying xFile = ... So the Swift compiler looks for the term xFile declared as a variable name in scope, to which something can be assigned. But the word xFile doesn't appear as a variable name in scope — just as the compiler is telling you. What does appear as a variable name in scope is xfile, which as far as Swift is concerned is a totally different name.

This isn't really a very useful solution. This change may bring down compile times but compile times are still atrociously slow. You change one line of one final class and it takes Xcode over a minute to recompile. That's criminal.

It's not actually hanging, it just takes a really long time. Keep your eye on the Finder status bar to see your hard drive slowly filling.

The answer from atbf is what helped me. You have to change the project setting build location and you have to close and reopen the project.

Me too, just started today. Feels like something belonging to Apple has suddenly started expiring.

Fixed. See https://stackoverflow.com/a/78421026/341994

I have zero users (except for me as owner) and I'm seeing this too

Plus the Contact page is blank so I can't even contact Apple to tell them about it.

This remains an issue. The checkbox is grayed out so you cannot check or uncheck it.

This is really lame. I absolutely do not want my devices to appear as destinations unless they are physically connected to my computer. Not only do they appear, but the build destination always defaults to one of them.

Same problem with my iPhone16e. Fixed by downloading Xcode 16.3 beta.

Not confined to SwiftUI; this also happens in UIKit. And it is still happening in Xcode 16.3 beta.

@DTS Engineer Yes, I'm having this issue in beta 3 as well. UIKit is never appearing in the documentation at all.