<ExternalDependency> is not a valid configured external dependency about tuist HOT 2 OPEN

Hey @sovata8 👋

Can you post a reproducible project that you worked with? Have you run tuist install after adding the dependency in your Tuist/Package.swift?

You can check out our fixture that showcases how to integrate dependencies via the XcodeProj-based integration: https://github.com/tuist/tuist/tree/main/fixtures/app_with_spm_dependencies

from tuist.

Hi, thanks for the reply.

The link to the sample project was a great resource!
I took it and reduced it to exactly my reproducible case, and can now observe where things fail.

I am attaching both my sample minimal reproducible project, and the modified Tuist's app_with_spm_dependencies.

tl;dr:
Things work only if the Alamofire package is defined under MyApp's Package.swift - if we define it in MyFramework's Package.swift, tuist-generate only works from the framework's folder, but fails for the whole app. Provided only MyFramework needs to know about the external dependency, ideally we'd like to define the it under MyFramwork, not globally.

The findings

(The explanation here applies to both attached projects, they have been reduced to the same reproducible issue)

So, in both projects MyApp -> MyFramework -> Alamofire.

Both MyApp and MyFramework have a Project.swift.
MyApp does not depend on 'Alamofire' (directly) only on MyFramework.
(Note, this is different from the original app_with_spm_dependencies where both the App and FeatureOne depend directly on Alamofire)

MyFramework's 'Project.swift' has as a target dependency:
.project(target: "FeatureOneFramework_iOS", path: .relativeToRoot("Features/FeatureOne"))

MyFramework's 'Project.swift' has as a target dependency:
.external(name: "Alamofire")

When it works and when it doesn't

We need to define the Alamofire package somewhere:

.package(url: "https://github.com/Alamofire/Alamofire", exact: "5.8.0")

If we define it under MyApp/Tuist/Package.swift, things work perfectly - the project generates, builds and runs. Alamofire is only linked to MyFramework as it should. We can also generate and build just MyFramework's project from its own folder, which is great.

But the above is somewhat confusing / unexpected / not ideal - by defining he package in the main app's Tuist/Package.swift, we make a 'hidden' dependency of MyFramework on a Tuist package defined under MyApp. Indeed, if we take this framework folder and put it elsewhere on our filesystem, it won't tuist-generate anymore, because the URL for Alamofire was defined in MyApp.

Ideally, we would like to be able to define the Alamofire package under MyFramework/Tuist/Package.swift.
Doing this actually works fine when generating MyFramework only, from its folder.
But then if we switch to MyApp, the generation fails with:

``Alamofire is not a valid configured external dependency

Zip files

• app_with_spm_dependencies_reduced_show_issue.zip
• MyApp_tuist_experiments.zip

from tuist.