Forage

My app and modules have some swift macros as external dependencies.

When warming the binary cache (tuist cache) for a project with a dependency on aws-sdk-swift (pinned to 1.7.53, which uses smithy-swift’s schema-based-serde codegen), the `Bi…

When a contributor forks tuist/tuist and enables Actions — which you have to do to run CI on your own branches — every on: push: branches: [main] and on: schedule workflow st…

Using Path.relativeToCurrentFile results in the callerPath being appended with the value from #file, which is the absolute path to the file, which in turn invalidates the manif…

During the production rebench of the snapshot-era cas-plugin (canary.20 against kura 0.15.2), a cold build resolved action-cache entries from a stale snapshot whose blobs had since…

This func spins up /usr/bin/open to open the project a…

I ran into a similar issue with https://github.com/tuist/tuist/issues/6188. I am using firebase directly with SPM instead of managing it through tuist.

I wanted to add test target for one of my app extension but it’s not supported by tuist.

A generated .xctestplan exists after the first tuist generate, but is deleted during the second consecutive generation.

With current Tuist and Xcode, Swift macro executables are emitted as framework search paths. Xcode passes them to the linker as -F arguments, but the macro products are executabl…