Pedro Piñera Buendía

@SubvertDev if you share a small example I can look at your specific issue.

@brentleyjones I'd be happy to take this one on, but I'd need some guidance on the Bazel side of things. Could you give me some pointers around what's the interface...

For anyone interested in looking into this one, Tuist copies the `Package.resolved` in and out from the generated `.xcodeproj`, since teams typically Git-ignore it, and that'd cause non-deterministic dependency resolution....

@tdkn how are you integrating those packages? If you are referencing those as `.external,` then `graphTraverser.hasRemotePackages` returns false because the function only considers remote packages, that are integrated using Xcode's...

Thanks @tdkn 🙏🏼. That's, in fact, what we do; after we generate the project, we call an `xcodebuild` command to resolve dependencies, and when it completes, we assume the resolved...

Thanks for the thorough analysis @woin2ee. What you describes makes total sense as potential cause of the issue. I wonder if [this PR](https://github.com/tuist/tuist/pull/6394) that I merged a couple of weeks...

> I don't fully understand the logic of graphTraverser, but in situations like [my minimal reproduction repo](https://github.com/tdkn/tuist-minimal-reproduction), I think that [graphTraverser.hasRemotePackages](https://github.com/tuist/tuist/blob/2263acd62339905c1305c83c07d7b8bd21a778da/Sources/TuistGenerator/Utils/SwiftPackageManagerInteractor.swift#L51) should be true because it indirectly depends on the...

Changes look good and work as expected. I'll merge [this PR](https://github.com/tuist/XcodeGraph/pull/57) and release a new version of XcodeGraph.

I'm working on getting CI green to merge it :)

I'm surfacing some useful context from a Slack conversation. My hunch is that this is an Xcode bug that we can't do anything about. To confirm the assumption, we'd need...