You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
Getting the following build error (Swift Package Manager):
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:
The text was updated successfully, but these errors were encountered: