Expo 57.0.11

Expo SDK 57.0.11 landed on npm on August 6, 2026, the newest patch in the 57.0.x line that began with the SDK 57.0.0 release on July 8. It arrives just two days after 57.0.10, keeping the patch cadence tight for the Expo Go and development-build ecosystem.

What's in the 57.0.x Patch Train

The 57.0.11 release follows a series of stability patches that have been consolidating around the expo/fetch networking layer and iOS runtime. Recent patches in the line have targeted race conditions in expo/fetch streaming — including out-of-order delivery of initial chunks on Android and URLSession delegate callbacks racing startStreaming() on iOS, which could deliver empty bodies on 200 responses or leave body streams open.

iOS Lifecycle and Deep Link Fixes

The patch series also carries the UIKit scene-based lifecycle adoption required for apps built against the iOS 27 SDK, so Expo apps launch correctly on the newest OS. That work included fixing Linking.getInitialURL() returning null and deep links being dropped when a URL cold-starts an app, plus marking ExpoAppSceneDelegate unavailable in extensions and widgets.

Upgrade Path

Upgrading is a standard bump: update the expo package in package.json to 57.0.11 and run npm install or npx expo install --fix. Users on SDK 57 with recent development builds will find the patch installs cleanly, and Expo Go users get it automatically through the app store channel as the update rolls out.