Do you remember how much I love Xcode? I love it. The only way I've found to have it pick up on change in xcconfig files is to rename the file, restart it so it fails and yanks the (definitely unhelpful) caching it does, then rename the file back and restart once more. That seems to make it somehow pick up on new/changed values in xcconfig files.

@tiennou Why is ENABLE_HARDENED_RUNTIME = YES added to the Dev.xcconfig example in Readme? If the local developer is not supposed to have this flag, then it shouldn't be there, right?

Also, does this make it no longer necessary to set up a Team ID and certificate? Was I solving it the wrong way in #376?

Because I suspected that, were you to provide the correct info in the Dev config, you might also consider enabling the runtime, and I changed the read me to make it more obvious that you could do that.

It does mean that, if your Schemes are set up correctly, any kind of build action triggered from Xcode will use the Debug configuration, and thus have any sort of "hard" signing disabled (hard, meaning you can't just "Sign local" or whatever, as per the rules on using the Hardened Runtime).

So now there's some sort of a 3-way configuration going:

• Debug with "soft" signing disabled, which should be the default.
• Debug with "hard" signing enabled, which you can enable with the appropriate settings in the Dev config.
• Release, with "hard" signing.
  and that means the build that actually goes out through CI and gets released doesn't really match what is usually run, unless you have forced it that way, and I get wary when things aren't really ever run.