-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Uncaught exception #27
Comments
The following error message doesn't indicate to me that this has anything to do with the size of the project.
Are you sure that:
|
Yes, I'm sure i pass a correct project path (I tried pass a .xcodeproj and just project folder, results are the same). The reason why I'm so sure, its because before that error message, i receive this warning:
( Changed paths to "XXXXXXX" ) |
Same here:
|
Looks like I've got the same problem here.
|
I'm having this problem too, but in my case, it seems to be related to some of the local dependencies in my Package.swift that use relative paths. On debugging Given my // swift-tools-version: 5.7
// The swift-tools-version declares the minimum version of Swift required to build this package.
import PackageDescription
let package = Package(
name: "SomePackage",
dependencies: [
.package(path: "../another_package"),
],
... The other package dependency is located at: |
On further investigation, this seems it might be because we have dependencies of dependencies that share the same dependency but resolve it at different relative paths. Live:
In both these examples |
Ok so looks like "user error" 😳 - Turns out the other package had the wrong relative path, for some reason this didn't cause errors in Xcode because the module was already resolved by an earlier package sharing the same dependency. Fixed the package issues and now it's working 😄 |
What happened?
Hi,
Then i try to use your tool on my large project with SPM, i receive this error output:
What are the steps to reproduce?
Really large project + SPM
What is the expected behavior?
Without error
The text was updated successfully, but these errors were encountered: