Kai Zhang

> Will this be of any use? > > https://docs.bazel.build/versions/main/command-line-reference.html#flag--incompatible_strict_action_env Yes. But on MacOS `--incompatible_strict_action_env` seems not ideal: [https://github.com/bazelbuild/bazelisk/issues/111#issuecomment-771847027](https://github.com/bazelbuild/bazelisk/issues/111#issuecomment-771847027)

I think we don't need `--apple_generate_dsym` or link strategy local for debugging. After some tests, we found that if the following conditions are met, the debug will work: 1. `-g`(`--apple_generate_dsym`...

Oh, `--features=oso_prefix_is_pwd` only be supported since Xcode 11. I don't know how many developers still use Xcode that are older than 11.

Thanks for your great job. This can help us a lot in building iOS applications with buildfarm. Is there any documentation about how to use this wrapper? We can help...

We enabled this wrapper in config: ```bash execution_policies: { wrapper: { path: "/path/to/macos_wrapper.sh" } } ``` works like a charm for us. We only enabled `CppCompile` and `ObjcCompile` for remote...

Currently, the action will fail if the required Xcode is not installed on the worker's platform. It would be nice if the worker could skip this action; other workers with...

https://github.com/kkpattern/bazel-buildfarm/commit/bc331988f2c58feaf1ecb7ef4b6f5d3cb17d125b I did a very quick and dirty implementation and it works for us.

> got the same error, but because no code sign was detected on the binary. > > are there any reasons we don't provide codesign on `ios_ui_test` and `ios_unit_test`? `ios_unit_test`...

I don't know if this will help, we are able to debug Android native in AndroidStudio build with bazel. The key is adding `build --copt="-fdebug-compilation-dir" --copt="/proc/self/cwd"`. We need similar flags...

If considering remote cache and remote execution, making sure debugging info doesn't contain absolute paths is a preferable way.