Same. Here's another post about this issue https://developer.apple.com/forums/thread/812634

I think we're having the same problem. Xcode Cloud build was stuck on Prepare Build for App Store Connect for 13 hours. App Store Connect was showing the build as "Processing". This morning I cancelled the build. Xcode Cloud status is Cancelled, but App Store Connect still showing as "Processing". Started a new build. Same issue. So now we have two builds stuck on "Processing". I contacted support with details. Case ID is 102802250079

Same here. If you download the xcodebuild-export-archive logs, you will probably see something like "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (502) for URL http://172.16.143.200:8089/.... ... error: exportArchive No signing certificate "iOS Distribution" found We had the same issue a couple of months ago, and it just went away the next day.

Same issue when building with Xcode Cloud. I think this happens every year - Apple publishes the News article but App Store Connect gets updated only the following day.

After some more investigation I think I found a workaround. In our case he problem is definitely related to SPM packages that contain .swift in the URL. I tried url encoding the dot (.) to %2e and it seems to fix the problem. So https://github.com/auth0/JWTDecode.swift.git becomes https://github.com/auth0/JWTDecode%2eswift.git Now the packages are resolved successfully both on Xcode Cloud and locally using Xcode 16 beta. Could someone please verify this?

Still crashes on Xcode 16 beta 4.

Same issue here. FB14248955 Not 100% sure, but I think in our case it is related to https://github.com/auth0/JWTDecode.swift and/or https://github.com/ashleymills/Reachability.swift dependencies. We can also reproduce it both by running xcodebuild and by simply trying to open the project in Xcode 16 beta.

Same here. Our builds became about two times slower (10 - 15 vs. 30 minutes). I think it started about a week ago.

Seems like this is fixed in Xcode 14.3.1 https://developer.apple.com/documentation/xcode-release-notes/xcode-14_3_1-release-notes