I’m coming across a flake issue error: module file 'module.pcm' is out of date and needs to be rebuilt: signature mismatch in some of my builds and am wondering if there’s anything on the Tuist side that could be affecting this? For the same commit, 2 builds with the same modules to generate/test can have one passing and one hitting this error.
Hey @irenalee 
Is that when using the binary cache or does the issue occur even when not using it? I’m assuming it’s related to modules with Objective-C code, could you confirm that?
In general, a bit more additional info would be appreciated here 
cc @waltflanagan is this something you’ve ever experienced? I believe you also quite some Objective-C left in your codebase (correct me if I’m wrong).
Hi Marek thanks for helping!
No we are not using the binary cache, happens during clean builds. And yes it does look like it’s related to Objective-C modules.
This currently happens when we are changing our test sharding algorithm. Instead of evenly splitting modules into 4 test shards, we are trying to split the shards by identifying “shard heads" (modules with no dependents in the test set), groups modules by their dependency relationships, and then merges smaller shards together until reaching the target shard count, ensuring balanced workload distribution while respecting module dependencies.