Seems as though this was a temporary issue that has since been resolved

Also getting this same error on Xcode 16.1 for watch app extension Info.plist

Oops! 504 HTTP error, not 502

Having the same problem today as well

It's very frustrating that this has been a problem for so long.... I and everyone else on the iOS team at work has to run git restore *.xcworkspace/xcshareddata/swiftpm/Package.resolved every. single. time. we switch branches. Sometimes we accidentally commit the deletion of Package.resolved into git and it screws up our Xcode Cloud pipeline. Any suggestions other than quitting & relaunching Xcode before & after switching branches? Has anyone had success with git hooks? I switched to SPM to avoid versioning issues with cocoapods + xcode. Cocoapods is volunteer-driven and xcode can make any change they want, regardless of what cocoapods supports. I don't want that bringing my development to a screeching halt, so I choose SPM. I miss the way that cocoapods works. My project is not a swift package. Why can't I define a Package.swift file (or something of the like) as the source of truth for the dependencies of my project, and just put Package.resolved in my .gitignore? Xcode could have the location of Package.swift as a setting in .pbxproj, and interpret when resolving dependencies. I get to decide when I want to update my package dependencies (xcodebuild spm install or xcodebuild spm update or something like that). Why not?? Am I missing something??

I'm still having this issue on Xcode 15.4

Seeing this happening a lot today, on more than 50% of xcode cloud builds. example: Could not resolve package dependencies: Couldn’t update repository submodules: Submodule 'external/catch' (https://github.com/catchorg/Catch2.git) registered for path 'external/catch' Submodule 'src/external/sha-1' (https://github.com/clibs/sha1.git) registered for path 'src/external/sha-1' Submodule 'src/external/sha-2' (https://github.com/kalven/sha-2.git) registered for path 'src/external/sha-2' Cloning into '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/external/catch'... error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 fatal: expected 'packfile' fatal: clone of 'https://github.com/catchorg/Catch2.git' into submodule path '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/external/catch' failed Failed to clone 'external/catch'. Retry scheduled Cloning into '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/src/external/sha-1'... error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 fatal: expected 'packfile' fatal: clone of 'https://github.com/clibs/sha1.git' into submodule path '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/src/external/sha-1' failed Failed to clone 'src/external/sha-1'. Retry scheduled Cloning into '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/src/external/sha-2'... fatal: unable to access 'http://github.com/kalven/sha-2.git/': The requested URL returned error: 502 fatal: clone of 'https://github.com/kalven/sha-2.git' into submodule path '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/src/external/sha-2' failed Failed to clone 'src/external/sha-2'. Retry scheduled Cloning into '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/external/catch'... Cloning into '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/src/external/sha-1'... fatal: unable to access 'http://github.com/clibs/sha1.git/': The requested URL returned error: 502 fatal: clone of 'https://github.com/clibs/sha1.git' into submodule path '/Volumes/workspace/DerivedData/SourcePackages/checkouts/realm-core/src/external/sha-1' failed Failed to clone 'src/external/sha-1' a second time, aborting Couldn’t update repository submodules:

Feedback ID: FB13660343

I am also having this problem with Product.currentEntitlement. We will check locally against the transaction's expirationDate value. Hopefully Product.currentEntitlement will always return the transaction with the higher expiration date... The language in the docs is maybe misleading here? Perhaps "entitled" means something other than "has access" when it comes to an auto-renewing subscription? Would be really helpful if someone from the StoreKit team could clarify.

We are also experiencing this same issue again, recently. Yesterday I filed 2 separate feedback assistant issues for 2 fresh cases: FB13299168 and FB13299461.

My builds have finally finished processing, and are now visible on TestFlight. I’m curious, is this a common occurrence that we should be aware of? What was the reason for the unusually slow processing time? Would be nice if we had some indicator of the progress of a build’s processing phase, so we can be sure as developers that we haven’t done anything wrong and just need to wait.

Same here, our builds are not successfully processing through App Store Connect, since noon ET today at the earliest. They are successfully uploading to App Store Connect, but they do not appear at all on the TestFlight page. We have Xcode Cloud builds running that should be deploying builds to internal & external testing on TestFlight, and they successfully archive and save the artifacts (green check in the Xcode Cloud log), but are not showing up in the list of downloadable artifacts in the Xcode Cloud build logs. Those builds made on Xcode Cloud are also not showing up in TestFlight, and the Xcode Cloud workflows get stuck and continue running ad infinity, running up our hour usage. We have tried from 2 separate developer machines to manually archive and upload, and those builds successfully uploaded, but have not yet appeared on App Store Connect on the TestFlight page. Really hope this is resolved soon, it's a major inconvenience to our release process.