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

Xcode 12.5 Beta 3 SPM: target 'SVProgressHUD' has invalid header layout: umbrella header found #1077

Open
ethanwa opened this issue Mar 4, 2021 · 3 comments
Labels

Comments

@ethanwa
Copy link

ethanwa commented Mar 4, 2021

Getting the following build error (Swift Package Manager):

target 'SVProgressHUD' has invalid header layout: umbrella header found at '~/Library/Developer/Xcode/DerivedData/collectors-cxrmmuolpcbfkpdnxggydzzxsvnh/SourcePackages/checkouts/SVProgressHUD/SVProgressHUD/SVProgressHUD.h', but directories exist next to it: ~/Library/Developer/Xcode/DerivedData/collectors-cxrmmuolpcbfkpdnxggydzzxsvnh/SourcePackages/checkouts/SVProgressHUD/SVProgressHUD/SVProgressHUD.bundle; consider removing them

This error is new to Xcode 12.5. Everything works just fine in 12.4. The issue could be because of this change in 12.5:

Swift Packages
New Features

The Swift Package Manager now builds package products and targets as dynamic frameworks automatically, if doing so avoids duplication of library code at runtime. (59931771) (FB7608638)

Swift packages that specify a 5.4 tools version can now explicitly declare targets as executable, which allows the use of the @main keyword in package code. (SE-0294, 47691185)

Swift Package Manager caches package dependencies on a per-user basis, which reduces the amount of network traffic and increases performance of dependency resolution for subsequent uses of the same package. If needed, you can disable cache use in xcodebuild by using the new -disablePackageRepositoryCache flag. (72204929)

@denandreychuk
Copy link

Did you find a solution?

@denandreychuk
Copy link

#1079

@stale
Copy link

stale bot commented Jan 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

@stale stale bot added the stale label Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants