CLI 4.195.4 fixes two consistency issues when working with SwiftPM and xcodebuild.
- Custom SwiftPM scratch paths are respected across the whole workflow. If you configure a custom scratch path via
installOptionsinTuist.swift, Tuist now uses it consistently for dependency cleaning, outdated-dependency checks, project generation, and editor heuristics. The default.builddirectory still applies when no custom path is set. - xcodebuild analytics are more stable. A crash that could occur when
tuist xcodebuildanalytics were parsed through the argument-reordering path is fixed. The uploaded analytics now capture the resolved subcommand and reordered arguments, and missing metadata falls back safely instead of causing a failure.