Live

iOS submissions failing on upload to App Store Connect

0

Expo reports that iOS submissions failed on upload to App Store Connect. EAS Submit, Apple Developer APIs, and related third-party services were degraded. Expo identified the issue as App Store Connect server errors. The incident is resolved and lasted 81 minutes.

State

Resolved

Started

Lasted

1 h 21 min

Worst impact

Degraded

Timeline

2 updates
20:2720:4721:0721:2821:48
DegradedUpdate postedTimes in UTC

Identified

1 h 21 min 100%

Updates

Times in UTC

As posted by Expo

Resolved
Identified

iOS submissions are experiencing elevated failures due to App Store Connect server errors. Submissions may fail while fetching app information or uploading a build. Affected users should retry their submission once Apple’s service recovers.

Affected components

4
EAS SubmitApple Developer APIsThird-Party Services - Apple Developer APIsExpo Application Services - EAS Submit

Expo in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

28

Days with an incident

23

Median duration

1 h 4 min

This incident

1.3× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h
median 1 h 4 min
90 days agoToday

Other Expo incidents

All incidents

Follow Expo

Your coding agent knows when Expo is down, and tells you when a failure is theirs, not yours. You can also get Expo incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "expo" and tell me if Expo has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=expo
Slack
/feed subscribe https://outages.live/feed.xml?providers=expo

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane