outages.live
Live
ExpoIncident ·

iOS submissions failing on upload to App Store Connect

ResolvedOfficial update
1

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.

State

Resolved

Started

Lasted

48 min

Worst impact

Degraded

Timeline

3 updates
22:2922:4122:5323:0523:17
DegradedUpdate postedTimes in UTC

Investigating

15 min 32%

Identified

32 min 68%

Updates

Times in UTC

As posted by Expo

Resolved

This incident has been resolved.

Identified

The issue has been identified. Apple is experiencing an App Store Connect issue that may delay iOS submissions or cause them to fail. We’re monitoring Apple’s status page at https://developer.apple.com/system-status/ and will share an update when this is resolved.

Investigating

User's may experience iOS submissions delayed with long build uploads to App Store Connect. Apple’s API is reporting prolonged pending or processing states, which will increase submission queue times

Affected components

2
EAS SubmitExpo Application Services - EAS Submit

Expo in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

29

Days with an incident

25

Median duration

1 h 7 min

This incident

29% shorter than the median

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

18 h
median 1 h 7 min
90 days agoToday

Other Expo incidents

All incidents

Expo·Partially Degraded Service

Expo reports that GitHub Webhooks were partially degraded. Expo resolved this incident after 36 minutes.

Resolved

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.

Resolved

Expo·Partially Degraded Service

Expo reports that GitHub Webhooks had degraded service. Expo resolved the incident. The outage lasted 24 minutes.

Resolved

Expo·Minor Service Outage

Expo reported degraded GitHub Webhooks. Expo resolved the outage after 99 minutes.

Resolved

Expo·Partially Degraded Service

Expo reports that GitHub API Requests did not work at full capacity. Expo resolved the incident after 36 minutes.

Resolved

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