Brentley Jones

I'm not sure you will be able to do #2, at least without putting these new files in the Project navigator, which is really tricky, especially with our custom Derived...

@erikkerber @pennig Us changing the validation build setting fixed this for local development, right? I think the main issue remaining is if someone tries to create an xcarchive and submit...

It's actually going to be a pretty tricky thing to tackle, and not a good First Issue to take on. This is because of the way that rules_swift uses an...

Thanks for the note! And I'll let you know if I think of something you can help with!

No need for a new issue, you can relate the PR to this one and update the description to link back to that PR. Thanks!

FYI: I've been using this with `--action_env=TOOLCHAINS=$TOOLCHAINS` to great effect.

https://github.com/bazelbuild/rules_swift/commit/1666670edadfe6e440b23d7142b0e21bf1043402

Ideally the `env` and `--test_env` will automatically be filled in autogenerated schemes. For Custom schemes maybe we can automatically fill in `--test_env`, but regardless we should allow specifying them, yes.

Which part are you still needing? Values set via `env` attribute on the rule, passed in with `--test_env`, both, or other? There is some background work happening on this, but...

It is not currently possible, but that's one way that we want to support soon.