Replies: 2 comments 3 replies
-
@everuribe Can you paste the full output and share your Package.swift file or Xcode package configuration? There's not enough to go off of what you've currently shared. It's possible you just need to reset your package dependencies, re-resolve them, or you may just have conflicting versions specified in your package. Since this doesn't appear to be a bug in the library I'm going to convert it to a Q&A discussion instead. |
Beta Was this translation helpful? Give feedback.
-
Hey. I just ran across this discussion as I was having the exact same error. Just wanted to share what worked for me in case others run across this as well. Everything worked locally, it was just on CI that we were having the problem. It is nothing related to the package but is only an issue when using the Obviously, these should be used with caution and only when using packages that you trust, but wanted to share in case it helps anyone else. 🙂 |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
We get this error when running
xcodebuild
operations. We specifically pinned all our dependencies and only updatedswift-case-paths
to1.1.0
and the error occurred in the package resolution phase. Could there be some versioning issue causing this?Environment
Additional context
Add any more context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions