Fail to add Package Collection in Xcode

[artemnovichkov]

Please describe the bug

Package Collection URL doesn't work.

Explain the steps needed to reproduce the bug

1. Navigate to Packages authored by Artem Novichkov
2. Copy Package Collection URL https://swiftpackageindex.com/artemnovichkov/collection.json
3. Paste the URL into Xcode during collection adding flow.

Got an error:
"Received invalid response at https://swiftpackageindex.com/artemnovichkov/collection.json. Please make sure it is a package collection URL."

What was the expected behaviour?

The collection added successfully.

Screenshots

I use Xcode 26.0 (17A324).

[daveverwer]

Thank you for reporting this @artemnovichkov, this is an unexpected situation.

The bad (or good, depending on how you look at it) news is that all package collections are broken, not just yours.

My first thought was that it was code signing, but the certificate is still well ahead of expiry and the signature is being generated. Instead, it seems to be an issue with the HTTP response. Loading a collection in a web browser works fine, but adding it to Xcode or SwiftPM directly returns an error. Luckily, adding it via SwiftPM gives a better error:

$ swift package-collection add https://swiftpackageindex.com/apple/collection.json                        
Error: Received invalid response for package collection at https://swiftpackageindex.com/apple/collection.json: Missing Content-Length header

I am continuing to look into it, but we have made no code changes to package collection signing recently, so it's an odd thing to just break on its own.

[daveverwer]

My guess as to why this has manifested now is that SwiftPM/Xcode in Swift 6.2 check for a content-length where earlier versions did not.

I have attempted a fix for this in #3888 but it needs deploying before it can be tested as we don't have local Cloudflare! 😬

[daveverwer]

I have turned the Cloudflare cache back on with the fix deployed and everything seems to be working now. Could you re-test as well please @artemnovichkov, and thanks again for reporting this!

[artemnovichkov]

@daveverwer thanks for a quick fix! It works now.