Marek Fořt

> @fortmarek How do I run the tests locally? As any other Xcode unit tests. Here's how to set things up: https://docs.tuist.dev/en/contributors/get-started#set-up-the-project-locally

I believe the issue is that you're specifying an SDK for a multiplatform target. I'd be curious to know how `xcodebuild` command behaves when the macro is integrated with the...

> My project only supports iOS which have one app target and a few static framework targets. I see – macros are in the end macOS executables, so technically you...

> I think the issue was that it required people to run the gettext command to extract the locales, but this doesn't go away with smaller files. Unless I'm missing...

> Up until now, for CAS, we piggybacked on the API specs and client of the server, relying on the fact that the endpoints were duplicated. This no longer works,...

Hey 👋 Yeah, the SPM integration doesn't use `GCC_PREFIX_HEADER` and we know using it is not ideal as commented [here](https://github.com/tuist/tuist/pull/5945#discussion_r1493303071) when we initially added this setting (the PR you linked...

Thanks for letting us know. I'm closing this issue then – we can reopen it this issue reappears on the latest CLI version.

> we have a dashboard that tracks coverage per module per branch but main is the only one that provides “true” coverage for the whole module since we run tests...

Closing as things seem to be working now. Please, open a new issue if you still run into this.

Hey @heyken 👋 Would you mind attaching a sample project? You can create a new one using `tuist init` and then apply your reproduction steps.