Gabriel Féron

FWIW, the only difference I can see between CI runners that are affected and the ones that aren't is that the `--output_user_root` is pointing to a symlink, pointing to another...

Progress report on the issue: _disabling_ the sandbox seems to make the issue go away, but I need to wait to confirm that. It's definitely a sort of Heisenbug. EDIT:...

The application only depends on a bunch of `ios_framework` and `apple_xcframework` (that have been imported). I'll try to figure out why the symbols are being generated for one of the...

> build --strategy=GenerateAppleSymbolsFile=local We actually tried this for quite a while and it didn't work. I'll try the advice from @nataliejameson and see if we can re-enable the sandbox on...

Thanks for the insight, it looks like `avoid_deps` is only supported for `apple_static_xcframework` but not for `apple_xcframework`. Right now, what works for us is to have something like: ```starlark apple_xcframework(...

I encountered the exact same issue in the past few weeks. It is related to a (current) hard limitation of `cargo metadata` which does not expose features per target platform....

> > One quick & dirty solution could be to add a `--host-triple` to `cargo tree` to be able to list `build-dependencies` for each platform Bazel is going to build...

We're already using `--incompatible_enable_cc_toolchain_resolution` to use an hermetic LLVM tooclchain (using https://github.com/grailbio/bazel-toolchain) and the `CC=clang` check prevents us to run `rules_swift`. Without this check, everything works fine and as expected,...

> I think the general assumption today to solve this is by doing CC=clang Yes, and this is the problem I'm trying to solve. You want to make sure `rules_swift`...

I would really love to see `libsignal` on crates.io as it would allow us to publish crates that make use of it, and it's pretty easy to update and make...