When you run tuist bazel setup, Tuist now performs an actual Remote Execution API handshake against the resolved cache endpoint before writing .bazelrc.tuist. If you set TUIST_CACHE_ENDPOINT to an override (or your server advertises a single endpoint), setup used to skip probing and could generate Bazel config pointing at a cache it never contacted, deferring an opaque failure to the first bazel build. Setup now fails fast with a clear error in that case, so you only get a working .bazelrc.tuist when the selected cache is genuinely reachable and authorized for your project.
Hive