The fetching takes also a while to complete so my hypothesis is that fetching works but it fails at the cloning step when writing to disk and it fails to access the directory or something. It looks like it is a permission/sandboxing issue when running Xcode build from a subprocess or something similar.Ī successful run looks like this: Resolve Package GraphĪ failed run like this: Resolve Package Graphīuild-wrapper: connect to /tmp/build-wrapper-socket.YiKkHY: Operation not permitted
Build xcode project from command line full#
This updates xcrun to point to the full collection of SDKs that Xcode provides. In Xcode, go to Preferences>Locations and select a specific set of command line tools from the drop-down. Thanks I will check that, but in the mean time I found a similar issue I think the cause of the issue could be the same as I experience. I very quickly realized that I must have been using the bare-minimum command line tools from when I first installed the machine. I couldn’t find any information on the returned code. The build-wrapper.log ends with these lines. When I run the same xcodebuild command without the build-wrapper package resolution works fine. I think the error is related to Xcode resolving Swift packages.
Xcodebuild: error: Could not resolve package dependencies:īuild-wrapper: connect to /tmp/build-wrapper-socket.27NmvM: Operation not permitted
When running the build wrapper command build-wrapper-macosx-x86 -out-dir sonar-reports xcodebuild -workspace MyProject.xcworkspace -scheme MyProject-Alpha -derivedDataPath derived_data_path build CODE_SIGNING_REQUIRED=NO Our codebase contains Swift & Obj-C code and we use Xcode 12. Hi, I have an issue with the build-wrapper command:
0 kommentar(er)
