--xcframework no longer works in v4 about tuist HOT 5 CLOSED

That parameter is now the default and only option, sorry for missing that in the changelog 🙏
Feel free to open a PR to update the changelog if you want 🙏

from tuist.

Sorry for not asking clearly, but before that we use --xcframeworks --destination device to only build cache for device not simulator (some frameworks are not available for simulator slice). What's the equivalent now in v4?

from tuist.

We currently always build for both. Ideally, you'd use tuist cache on main, so that the command is not run that often – that should make the compile time hit smaller.

from tuist.

Yes but the problem is the cache cannot be built at all, some frameworks is closed-source and prebuilt framework without simulator slice, so the cache warm will fail when it tries to create xcframework for both device and simulator.

from tuist.

Caching for device only is currently not possible. We could add support for this, would you mind creating an issue describing your need?

from tuist.