Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing a dependency breaks tuist generate. #6263

Closed
hbanzon opened this issue May 8, 2024 · 1 comment · Fixed by #6298
Closed

Removing a dependency breaks tuist generate. #6263

hbanzon opened this issue May 8, 2024 · 1 comment · Fixed by #6298
Assignees
Labels
type:bug Something isn't working

Comments

@hbanzon
Copy link

hbanzon commented May 8, 2024

What happened?

After another developer had removed a third party dependency, other developers are running into this issue after attempting to run tuist generate:

$ tuist generate
Loading and constructing the graph
It might take a while if the cache is empty

The following warnings need attention:
The artifact for binary target PayPalCheckout of package PayPalCheckout cannot be found.
Consider creating an issue using the following link: 

How do we reproduce it?

Developer A will do the following:

  1. Remove a third party dependency, for us it was PayPalCheckout (but it can be any project)
  2. Check in the change to the repo

Developer B will subsequently do the following:

  1. Checkout the change from the same repo
  2. Run tuist install
  3. Run tuist generate

This happened to folks using Tuist Cloud and not using Tuist Cloud.

Error log

The artifact for binary target PayPalCheckout of package PayPalCheckout cannot be found.
Consider creating an issue using the following link: https://github.com/tuist/tuist/issues/new/choose

macOS version

14.2.1

Tuist version

4.10.1

Xcode version

15.3

@hbanzon hbanzon added the type:bug Something isn't working label May 8, 2024
@pepicrft
Copy link
Contributor

pepicrft commented May 15, 2024

I set this one as high-priority. Our hunch is that the SPM might be leaving some internal files with an updated state, and that causes our logic, which assumes an up-to-date state in those files, to fail. We might need to alleviate the strictness until Apple fixes that in the SPM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants