Post

Replies

Boosts

Views

Activity

Reply to XcodeCloud fails while Resolving Dependencies
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?
Jul ’24
Reply to Random exportArchive 70 Error Code When Using Xcode Cloud for Build
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.
Apr ’25