-
Notifications
You must be signed in to change notification settings - Fork 301
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
xcodebuild DocC error with Xcode 14 #234
Comments
I have created a repository with the minimum code required to see the error: |
@fraune Have you found any solution so far? We've seen this error showing up in another project: malcommac/SwiftDate#799 But according to the date of the Swift forums thread, this issue should be unrelated to Xcode 14. |
Haven’t found a solution yet. I am guessing the guys on the Swift forums were getting the same error but unrelated to this package. Downgrading to Xcode 13.4.1 is my current workaround. |
Is that error preventing editing/opening of the package? I'm told it should be harmless hm... |
I also experienced this issue and had to downgrade to 1.3 |
We're looking into this, thanks for reporting |
Yea, I didn't have trouble importing or using this package when programming or running the app on a device through Xcode. Just having trouble building my app with xcodebuild when this dependency is in my project. |
Hi, any news on this? i have same problem |
Hello, same problem here. Downgrading to Xcode 13.4.1 solved the problem. (temporarily, until I will really need Xcode 14) To clarify : issue only appear on command line build (using |
This seems fixed for me after renaming the "Docs.docc" folder. .package(url: "https://github.com/kalinjul/swift-log.git", exact: "1.4.4-fix"), |
@kalinjul , that would break the doc generation with SPM's docc plugin, no? |
Quite possible, but i did want a working library more than documentation. |
I'm unable to reproduce any actual build issue myself, but I do see the |
@neonichu iiuc you are saying the @sebsto @javichaques @geertbleyen or others that reported broken builds - could you provide more information on what prevented the build from succeeding? |
@tomerd, hmmm, for some reason I can't get it to fail the build on that error, it seems to just pass it by in my smaller repro environment. But it still shows this error: |
@tomerd here are steps to reproduce on my project
Building from Xcode GUI works. |
thanks @sebsto the actual build error is
the docc output here is a red herring afaict. of course there is still the questions of why this is failing only with |
Packages aren't really supported in legacy-style builds, the project builds for me when passing |
@tomer agreed but I though the Atomic lib build failed to build because of the error in the preceding steps. |
I'm a bit confused. What is this 'less / not supported path' or legacy-style builds for building projects with packages? for example: |
As said above, packages aren't supported in legacy-style builds (building without a scheme, which is only possible through xcodebuild), scheme-style builds are of course fine, whether through the IDE or xcodebuild. |
@neonichu @tomerd confirming that
|
As of Xcode 14.0.1, this issue is not blocking me. I still get the warning message that I listed in my OP, but it no longer prevents me from running my builds. |
Expected behavior
My team and I normally build our app with a CLI command like this:
Actual behavior
After updating Xcode from 13 to 14, running our
xcodebuild
command now fails with the following error:Steps to reproduce
swift-log
(https://github.com/apple/swift-log.git) as a Package Dependencyxcodebuild -quiet
If possible, minimal yet complete reproducer code (or URL to code)
I found a related issue on the Swift forums that was posted a few months back: https://forums.swift.org/t/xcode-and-swift-package-manager/44704
I tried modifying the
xcodebuild
flags forderivedDataPath
andclonedSourcePackagesDirPath
, but it did not appear to change how this issue was affecting my builds.SwiftLog version/commit hash
Swift & OS version (output of
swift --version && uname -a
)The text was updated successfully, but these errors were encountered: