iOS submissions failing on upload to App Store Connect
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 updatesIdentified
1 h 21 min 100%
Updates
Times in UTCAs posted by Expo
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
4Expo in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
23
Median duration
1 h 4 min
This incident
1.3× the median
Other Expo incidents
All incidentsExpo·iOS submissions failing on upload to App Store Connect
Expo EAS Submit had degraded iOS submissions to App Store Connect. App Store Connect reported long pending or processing states, which delayed or failed iOS submissions. Expo reports that the incident is resolved. It lasted 48 minutes.
Expo·Partially Degraded Service
Expo reports that GitHub Webhooks were partially degraded. Expo resolved this incident after 36 minutes.
Expo·Partially Degraded Service
Expo reported a partially degraded service that affected GitHub Webhooks. Expo says the incident is resolved. The outage lasted 30 minutes.
Expo·Partially Degraded Service
Expo reports that GitHub Webhooks had degraded service. Expo resolved the incident. The outage lasted 24 minutes.
Expo·Minor Service Outage
Expo reported degraded GitHub Webhooks. Expo resolved the outage after 99 minutes.
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.
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.
https://outages.live/feed.xml?providers=expo/feed subscribe https://outages.live/feed.xml?providers=expoFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane