Expo: Broken artifacts for EAS builds triggered between ~8:34 AM GMT and ~10 AM GMT
Timeline of updates
- resolved
The faulty deployment introduced a bug that caused build artifacts to not be uploaded correctly to storage buckets. Developers trying to download the artifacts of affected builds could see an error like "The specified key does not exist. No such object: ..." The issue also affected submissions trying to upload the builds with broken artifacts. The developers who encountered the issue saw an error like "Failed to download the archive file (Response code: 404 Not Found)" The issue was identified by the Expo team and the deployment was reverted at around 10 AM GMT. The charges for all of the broken builds were waived.
From Expo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.expo.dev (opens in new tab). Expo profile · Recent Expo incidents · Markdown · JSON