Expo: iOS submissions failing due to upstream issue
Timeline of updates
- resolved
Between April 3rd, 8 PM and 10 PM UTC we have seen an increased number of iOS submissions failures. They seem to have been caused by an Apple servers outage (we were getting "Internal server error" HTTP responses when not expected). [Application Loader Error Output]: [ContentDelivery.Uploader.6000039FC140] RETRIEVE UPLOAD OPERATIONS (UPLOADING ASSET DESCRIPTION): received status code 500; internal server error. (500)
From Expo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.expo.dev (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Expo, started 2025-04-03 20:00 UTC, resolved after 0 min, 1 update(s).
- Title
- iOS submissions failing due to upstream issue
- Vendor
- Expo
- Date
- URL
- https://rewindex.com/company/expo/incidents/dt61qqlx8h87
Expo profileRecent Expo incidentsAll outages on April 3, 2025Expo in April 2025MarkdownJSON