Forage

When attempting to build or cache each time we bump external dependency versions we see the following build error citing missing symbols for a specific architecture. The problem so…

When a local SPM package declares a target with the .embedInCode(_:) resource rule (available since PackageDescription 5.9), Tuist fails to decode the package descriptor produced…

Splitting this out from #10366 (thread).

When trying to run our builds with Xcode 26 on Github actions. The sandboxing seems to be failing unexpectedly. Specifically when we run Xcode-select to select a specific Xcode ver…

The shared module (binary) cache is serving a broken ArgumentParser xcframework that fails Swift module resolution. Any cache-on build that pulls it fails with:

Currently, we store module cache binaries only after building all the modules are built.

Since the single-host gRPC change (#11356), KuraInstance.spec.grpcPublicHost is vestigial:

Originally raised here: https://community.tuist.dev/t/bundle-analysis/849

Right now, it’s easy for engineers to forget to run tuist setup cache, leading to way slower builds because Xcode keeps trying to connect to the socket, only to time out.

I just recently updated from a very old version of Tuist (4.70.0 -> 4.200.5) and found a change in the behavior of the tuist test command. It appears that it will always scope do…