Expo 57.0.12

I saw Expo 57.0.12 land on npm on August 10, 2026 and, as usual, I upgraded a test project the same morning so you don't have to. Spoiler: it's a quiet patch, but quiet is exactly what you want from a mobile framework in the middle of a release cycle.

The Upgrade Itself

Bumping expo from 57.0.11 to 57.0.12 was a one-line change in package.json followed by npx expo install --fix. No config migrations, no new native folders, no surprises in the prebuild step. Total time from start to a warm dev server: about four minutes.

That matches the pattern I've seen all through the 57.0.x series — these patches ship fast and break nothing. The full changelog for the line is honestly the more interesting read, because it shows where the team has been spending its energy: stability around expo/fetch, the iOS 27 SDK scene lifecycle, and deep-link handling.

What the 57.0.x Line Has Been Fixing

• expo/fetch streaming races — URLSession delegate callbacks could deliver an empty body on a 200 response or drop chunks mid-stream. The fixes landed across recent patches, and my streaming tests have been rock solid since.
• iOS 27 SDK scene lifecycle — apps now launch correctly under the UIKit scene-based lifecycle, and Linking.getInitialURL() no longer returns null when a deep link cold-starts the app. I tested this on a real device with a universal link and it fired first try.
• Async imports — import() via asyncRequireModule now resolves to a proper thenable shape instead of a broken promise, which fixes a class of flaky route-level code-splitting bugs.

Worth It?

Verdict: update. There's no new feature here that will change how you write code, but patch releases on the SDK 57 line have been consistently removing sharp edges — and 57.0.12 sits on top of all of them. If you're already on 57.0.11, the jump costs you nothing. If you're still on SDK 56, this is a good moment to plan the move.

One tip: after upgrading, run npx expo-doctor to confirm your native projects are in sync, and give your deep links and any expo/fetch usage a quick smoke test.