XCode Cloud is literally broken for 2 months now

Since I started using XCode Cloud, my builds regularly failed due to networking issues, which is really just embarrassing. How can a company like Apple, which praises itself with a high-quality standard, ***** this up so badly?

However, since two months ago literally every single build started failing for "connection reset by peer"

My ci_post_clone.sh runs this code and surprisingly enough that step succeeds most of the time.

#!/usr/bin/env bash
set -e

brew install cocoapods
curl -s "https://get.sdkman.io" | bash
source "$HOME/.sdkman/bin/sdkman-init.sh"
sdk install java 20.0.1-tem

# cd into actual project root
cd ../../../
./gradlew app:ios:podinstall

However in the archive task the errors start rolling in

2023-08-30T22:27:24.108163427Z	Could not resolve com.google.devtools.ksp:symbol-processing-api:1.9.0-1.0.11.
2023-08-30T22:27:24.108168428Z	         > Could not get resource 'https://repo.maven.apache.org/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'.
2023-08-30T22:27:24.108173676Z	            > Could not GET 'https://repo.maven.apache.org/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'.
2023-08-30T22:27:24.108181057Z	               > Got socket exception during request. It might be caused by SSL misconfiguration
2023-08-30T22:27:24.108186894Z	                  > Connection reset by peer
2023-08-30T22:27:24.108206745Z	Could not resolve com.google.devtools.ksp:symbol-processing-api:1.9.0-1.0.11.
2023-08-30T22:27:24.108213605Z	         > 
2023-08-30T22:27:24.108219500Z	Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'.
2023-08-30T22:27:24.108234940Z	            > 
2023-08-30T22:27:24.108239423Z	Could not GET 'https://dl.google.com/dl/android/maven2/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'.
2023-08-30T22:27:24.108662595Z	Got socket exception during request. It might be caused by SSL misconfiguration
2023-08-30T22:27:24.108669328Z	
2023-08-30T22:27:24.108716268Z	                  
2023-08-30T22:27:24.108725059Z	> 
2023-08-30T22:27:24.108732903Z	Connection reset by peer
2023-08-30T22:27:24.108740596Z	      
2023-08-30T22:27:24.108748688Z	> 
2023-08-30T22:27:24.108759002Z	Could not resolve com.google.devtools.ksp:symbol-processing-api:1.9.0-1.0.11.
2023-08-30T22:27:24.108820147Z	         > 
2023-08-30T22:27:24.108829571Z	Could not get resource 'https://maven.pkg.jetbrains.space/public/p/compose/dev/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'.
2023-08-30T22:27:24.108837310Z	            > 
2023-08-30T22:27:24.108844471Z	Could not GET 'https://maven.pkg.jetbrains.space/public/p/compose/dev/com/google/devtools/ksp/symbol-processing-api/1.9.0-1.0.11/symbol-processing-api-1.9.0-1.0.11.pom'.
2023-08-30T22:27:24.108860417Z	               
2023-08-30T22:27:24.108866956Z	> Got socket exception during request. It might be caused by SSL misconfiguration

So because it is highly unlikely or actually statistically impossible that repo.maven.apache.org, dl.google.com and maven.pkg.jetbrains.space all always decide to crash simultaneously whenever I run an XCode build for the past 3 months, this has to be an issue on their part. Did they suddenly stop allowing internet connections in the archive step?

Apple Support was just useless and aksed for irrelevant and impossible information like:

  • my browser
  • my ipa file (of a failing build?!)

Does anyone have any idea what causes this or has contacts to someone at apple which can fix this?

Post not yet marked as solved Up vote post of Schlaubi Down vote post of Schlaubi
2.1k views

Replies

I have the same problem.

I'm deploying an Ionic project. Xcode Cloud was ok for the best part of this year. Now 9/10 builds fail with network errors to NPM packages. It's not NPM because the project builds fine on my own runners

I would of course love to build the iOS project on my own runners but Apple and their policies mean having own cloud runners for iOS is very expensive because "blah blah on the metal"

XCode is lame compared to every other IDE. Xcode Cloud infrastructure seems to be running on a lemon connected to a potato. App Store Connect application loads slowly. Apple's support for developers is so bad.

I wonder if anyone on their team has ever worked on anything other than Apple and have no idea how good things should actually be compared to what they offer.

(written in anger while waiting for yet another build to fail)

  • Same. Developing an Ionic Angular project. When my post clone script reaches the line for "npm ci" there is an npm error. Sometimes it works but sometimes it doesn't. I am not sure how.

    Mostly I'm on my Windows PC. I want my iOS app deployed on push. It is nice to automatically deploy iOS app to testflight without being forced to use a Mac. Still can't figure out how to solve the issue below.

    "npm ERR! code ECONNRESET"

Add a Comment

Yep, same thing here, started a few days ago, used to work consistently until then! I sent a support request to Apple, but no reply yet...

+ npm install

npm ERR! code ECONNRESET

npm ERR! syscall connect

npm ERR! errno ECONNRESET

npm ERR! network request to https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.0.tgz failed, reason: connect ECONNRESET 104.16.2.35:443

I am also experiencing this issue and no reply from Apple still.

Exactly the same problem here, ECONNRESET and other random network issues. I have been trying 20+ times per day, and since Monday I have only been able to get one single npm ci and pod install to complete. Incredibly frustrating.

I believe Apple has implemented a restriction on the number of external connections. For problem with npm ci try adding: npm config set maxsockets 3

or less then 3 . By default it's "15" See docs: https://docs.npmjs.com/cli/v9/using-npm/config#maxsockets

In the end should be:

npm config set maxsockets 3
npm ci
  • Thank you. That was the issue for me.

Add a Comment

I have the same issues trying to download npm packages. With a random errors:

npm ERR! errno ECONNRESET

npm ERR! network request to https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz failed, reason: 

npm ERR! network This is a problem related to network connectivity.

or this one:

npm http fetch GET 200 https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz 94016ms attempt #3 (cache miss)

Error
The Post-Clone script timed out. No activity has been detected on stdout or stderr in 15 minutes.
  • I am facing the same issue even though I have added: npm config set maxsockets 3

    The issue occurs approximately once or twice in every 10 builds.

Add a Comment

I'm also experiencing this issue when I'm trying to execute "npm ci" I have also set the "npm config set maxsockets 3" parameter, but no success.

This is the error I receive:

npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm ERR! code 1
npm ERR! path /Volumes/workspace/repository/node_modules/sharp
npm ERR! command failed
npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-*** rebuild && node install/dll-copy)
npm ERR! sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.5/libvips-8.14.5-darwin-x64.tar.br
npm ERR! sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies
npm ERR! sharp: Installation error: connect ECONNRESET 140.82.113.4:443
npm ERR! A complete log of this run can be found in: /Users/local/.npm/_logs/2024-01-26T13_17_09_670Z-debug-0.log

Any other ideas how this can be resolved?

Hello? Is there any Apple responsible person able to solve that issue? can anyone explain why this is happening?

I am also experiencing the issue with ECONNRESET during npm ci.

I have nothing useful to add other than another voice begging for a fix.

It is impossible that Apple has not seen this yet. I have been following this thread and regularly checking back for months. Is there anything more effective we can do to get this resolved?

  • Worked around this by adding retries for install command, but this is consuming additional minutes. Not ideal.

Add a Comment

I've stopped using Xcode Cloud about 2-3 months ago because of this issue. It keeps failing randomly during the 'npm ci' or 'npm install' processes with the error 'The Post-Clone script timed out. No activity has been detected on stdout or stderr in 15 minutes.' It seems to fail at different points during the process each time. For instance, last time it failed while installing 'phin @2.9.3', and another time on 'uglify-es @3.3.9', and so on. I've resorted to using Xcode to build locally and then upload to the Apple Store, but this is quite frustrating -- we've already encountered a few bugs that were introduced due to this manual build process

My Xcode Cloud builds have also stopped working due to this issue forcing me to go back to manual builds and uploads. It's been huge setback. I'm responsible for 5 Capacitor hybrid apps that require many npm dependencies.The Post-Clone script timed out. No activity has been detected on stdout or stderr in 15 minutes. while npm ci. For me, the last logs I see are consistently:

npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
cemap-codec instead

Same for me, i switched to bun and install now works i just have the issue when i do npx @capacitor/assets@latest i will try bun run

I maintain a tutorial article here for the people using npm and JS apps: https://capgo.app/blog/how-to-build-capacitor-app-in-xcode-cloud/

Same here, since 4/5 days npm commands fails with ECONNRESET, i was previously able to mitigate this using a Verdaccio proxy, but now the problem persists and every build fails.

I have some apps that I manage where the build is run via Yarn, and those seem to succeed while another app I manage that uses NPM has a 50% or higher failure rate. Using the suggestion above npm config set maxsockets 3 helped and I lowered it to 1 which seemed to help a bit more but I cannot figure it out. Only solution that I can say works for me is switching to Yarn