Brentley Jones

I've seen otherwise. I was going to have to set lots of LLDB settings, and it wouldn't fully cover every situation that `_LocalDebugOptions` would cover. I'll test again next week...

I re-read your changes. They are technically correct, since setting `target.swift-framework-search-paths`, `target.clang-module-search-paths`, etc. will work around _most_ issues. I asked about this here though: https://ios-dev-at-scale.slack.com/archives/C019VJ6LK2T/p1651788632722239, and my main concern is...

> Setup a `lldbinit` that restores any of the options that were intended to be set in the `swiftmodule` files It does require more than you state in the PR...

To support multiple Xcode configurations (i.e. Release and Profile in addition to Debug) we will probably need a wrapper script around the `bazel run` invocation, to be able to capture...

We now have a wrapper script in the form of the ["runner"](https://github.com/buildbuddy-io/rules_xcodeproj/blob/c20d4760635faddd2437b7991d5ec69b39aa1d83/xcodeproj/internal/xcodeproj_runner.bzl). It's not too customizable right now, but we now also support pretty arbitrary config via [configs in `.bazelrc`...

Sadly transitions can't apply `--config`. But yes, that's the goal of the 0.8 Milestone.

Even though the configuration key is different, that doesn't impact the action result cache checking.

I don't think it shows up with query. gRPC log will show the same action digest though.

I haven't. I've been bit by it a couple more times since then though.

Let's keep this open until that ships.