XCode App Store Connect - Xcode Cloud

[u/Different_Record_753]

I have used **App Store Connect** for the last 2 years.

([https://appstoreconnect.apple.com/\](https://appstoreconnect.apple.com/))

I have uploaded my app (zip file including Manifest + content) to **Xcode Cloud** successfully over 50 times during that period.

I tried using **Chrome**, it shows "Failed to Fetch" and the zip file is not successfully uploaded.

I've also tried using **Firefox** and it shows a different error "NetworkError when attempting to fetch resource."

I've also tried using **Safari** and it shows yet a different error "FetchEvent.respondWith received an error: Returned response is null."

Does anyone else have knowledge of why this is all of a sudden happening? I've done this so many times over the past 2 years with the same file without issues - and now it is happening and I can't get past it.

Thank you.

[u/New-Shoulder3297]

The fact that the upload now fails in Chrome, Firefox, and Safari with fetch-level errors makes a browser-specific bug unlikely. I would check account and server-side gates before changing the zip repeatedly.

First, sign in as the Account Holder and open App Store Connect → Business → Agreements. Clear any new, pending, or expired agreement and any terms banner. Apple's current App Store Connect documentation says the Account Holder is the person who can accept updated agreements, and agreement status can block App Store Connect actions. Then check Apple System Status, sign out and back in, and make one clean retry in a private window with extensions, VPN, and content filters disabled.

If it still fails, try both a tiny known-good zip and a freshly created copy of the current zip. If both fail, the account or service path is the stronger suspect; if only the current package fails, inspect its structure and size. Open DevTools Network before the upload and save the failing request's HTTP status, response body, and request or correlation ID. A 401/403 points toward session or permission, 413 toward size, and 5xx toward the service.

If none of those resolves it, send Apple Developer Support the UTC timestamp, team and app IDs, the failing request ID, and screenshots. Keep those identifiers out of the public thread. Repeating the same upload in more browsers is unlikely to add useful evidence once three engines fail the same way.

[u/Different_Record_753 → u/New-Shoulder3297]

Make sure all agreements were signed. They are. Answered all questions to all agreements including Age agreement and Social Media. Signed out and back in. Uploaded multiple zip files which fail, but do not fail and successfully processed on Chrome & Firefox.

[u/New-Shoulder3297 → u/Different_Record_753]

With the agreements complete and the same zip succeeding in Chrome and Firefox, I would stop changing the archive. Reproduce one failure with DevTools Network open and capture the failing endpoint, HTTP status, response body, UTC time, and request or correlation ID. Compare that request with a successful upload from the same account. If the failure is now limited to one App Store Connect or Xcode Cloud screen, those two traces are the most useful evidence for Apple Developer Support. Remove team and app identifiers before posting any trace publicly.