Nuke: xcodebuild show issues: Cannot open "*.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

Downgrading to Xcode 13.4.1 worked for me as well 👍

I had a similar error on our CI with another project. Downgrading Xcode from 14.0.1 to 13.4.1 fixed the issue

~I really one to add one a solution here (for anyone with the same experience) which is really weird and crazy:~ ~In my case the signing certificate has been expired and then this issue came up.~ ~I renewed my distribution certificate and everything is back up again!~

~Cheers.~

The real cause was NOT the .docc warnings for the build to fail, to make that clear.
Please check out the raw xcodebuild log, remove any log prettifier, like xcpretty, because they might swallow some error info.

I totally agree. This is just a warning when using xcodebuild, but it is not the real reason a build fails. It just looks like that, but you need to check the raw build log and will find the real build failure reason.

Regarding xcpretty: It should be replaced by xcbeautify.

Update: it appears to be a non-blocking issue. I tested it in the following project:

test-nuke-docc.zip

xcodebuild archive -scheme test-nuke-docc -configuration Release

There are also other reports, for example in swift-log that confirm that it’s non-blocking.

Tools like xcpretty often hide the real build failure reason. For example, when I was testing it, I forgot to set-up signing and the output with xcpretty was the following:

2023-03-04 13:09:14.372 xcodebuild[11230:8233966] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x60000374de00: name:PulseUI.docc path:group:PulseUI.docc> Failed to load container at path: /Users/kean/Library/Developer/Xcode/DerivedData/test-pulse-docc-arvchnsawevpdlaqezsiwotyddpb/SourcePackages/checkouts/Pulse/Sources/PulseUI/PulseUI.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "PulseUI.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "PulseUI.docc" as a "Swift Package Folder" because it is already open as a "Folder".}
▸ Clean Succeeded
** ARCHIVE FAILED **

If you remove xcpretty, it shows the real reason of the build failure:

/Users/kean/Desktop/test-pulse-docc/test-pulse-docc.xcodeproj: error: Signing for "test-pulse-docc" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'test-pulse-docc' from project 'test-pulse-docc')
** ARCHIVE FAILED **

@Sam-Spencer

We’ll be trying again when Xcode 14.1 rolls out.

I tried Xcode 14.1 RC and it’s not fixed. Please upgrade to Nuke 11.3.1 that has a workaround for this issue.

I’m able to reproduce it. There seems to be an issue with xcodebuild and .docc folders in package Sources/. It is the Apple recommended way to setup DocC for Swift packages. I fixed it in 11.3.1 by temporarily removing .docc folders from Swift packages.

Just a heads up, our team at work is also experiencing this issue with other Swift Packages (e.g. Swift Protobuf) after upgrading our Azure CI pipelines to Xcode 14.0.1 and iOS 16 SDK. Can’t say for certain, but it seems to be a bug on Apple’s side of things. And, for what it’s worth, from what we’ve been able to tell in our diagnosis of the issue you should be able to build and archive successfully regardless of the warning.

I had a similar error on our CI with another project. Downgrading Xcode from 14.0.1 to 13.4.1 fixed the issue – @simawn

Our resolution was similar after a lot of back and forth with the folks at Azure. Seems like something undocumented changed in Xcode 14 with xcodebuild. We’ll be trying again when Xcode 14.1 rolls out.