Expo SDK 58 upgrade plan for production React Native apps. Expo SDK 58 brings iOS 27's scene-based life cycle, React Native 0.88, the Strict TypeScript API, R8 by default on Android and server output in Expo Router. A three-week upgrade plan for founders with a React Native app already in production. Umair Abbas Oct 26, 2026 · Updated Oct 28, 2026 * Expo * Expo SDK 58 * React Native * React Native 0.88 * iOS 27 * UIScene * Mobile upgrades Expo announced SDK 58 on October 14, 2026. It is built for iOS 27, ships React Native 0.88, and on paper the upgrade is one command. In practice it is the most consequential Expo release of the year for teams with a production app, because several defaults changed at once: how iOS starts your app, how strict TypeScript is about React Native imports, how Android release builds are shrunk, and how Expo Router renders on the web. This is the plan Code Flamme use with founders whose React Native app already takes money or runs a field team. The short version: start the upgrade on a branch this sprint, test on real devices, and do not let the new Expo Go timing push you into upgrading production early. Why SDK 58 is not a routine bump. Expo's release notes are direct about the iOS side: iOS 27 requires the UIKit scene-based life cycle, and apps built with the iOS 27 SDK get it automatically. SDK 58 moves Expo apps onto that life cycle so they launch correctly on iOS 27. Running npx expo prebuild now generates a SceneDelegate.swift and a scene manifest entry in Info.plist, and the window is created by the scene delegate rather than in didFinishLaunchingWithOptions. Expo forwards URL, user activity, Handoff, life cycle and quick action events to ExpoAppDelegate overrides and subscribers, so config plugins built on those keep working. The risk sits elsewhere: bare React Native apps, teams that manage the ios directory by hand, and native SDKs that override app delegate methods directly. If your push, SSO or payment vendor tells you to put window setup in the AppDelegate, that is the first thing to test. SDK 58 also prepares apps for iPhone Duo, where iOS moves bars into a side rail and windows resize as the device folds. Code Flamme covered the layout side in its iPhone Duo readiness guide for B2B iOS apps. The breaking changes that cost real time. Strict TypeScript API. React Native 0.87 made the Strict TypeScript API the default, and SDK 58 picks it up. Deep imports from react-native/Libraries/* become type errors, and ref types change shape. Expo documents a temporary opt-out through a customConditions setting in tsconfig.json, but says that opt-out is set to be removed after React Native 0.89, which the React Native release schedule lists for December 7, 2026. Treat the opt-out as a few weeks of breathing room, not a plan. Removed React Native APIs. InteractionManager is gone in favour of requestIdleCallback, along with the Touchable root export, the Modal animated prop and several deprecated StatusBar props. Older internal component libraries tend to lean on exactly these. R8 on by default for Android release builds. New Android templates enable minification in release builds. That shrinks apps and helps startup, but libraries that rely on reflection may need ProGuard keep rules. A crash that only shows up in a release build is the classic symptom, so run your QA pass on a release build. Environment handling. Expo CLI now sets NODE_ENV from the command you run and loads the matching .env file. Custom build configurations such as Staging use production. If your staging app quietly relied on .env.test or .env.staging being picked up, check which API endpoints it actually calls after the upgrade. Expo Router. Data loaders, server rendering and middleware are now stable. Router projects default to server output on the web, rendering HTML on each request instead of prerendering at export. If you host the web build as static files, set the output back to static deliberately. Expo SDK 58 upgrade checklist Branch created; npx expo install expo@^58.0.0 -fix npx expo-doctor@latest passes android/ and ios/ regenerated (CNG) or upgrade helper applied AppDelegate overrides and native SDKs reviewed for UIScene Deep link, push open, SSO callback tested on device Strict TypeScript errors fixed (no reliance on opt-out) Android release build tested with R8 Staging env vars verified after NODE_ENV change Router web output set deliberately (server or static) New development build created Expo Go timing is a trap for production teams. Expo says the new Expo Go for SDK 58 will reach the App Store and Google Play within a few weeks of the release, and that it will support only SDK 58. Until then, npx create-expo-app still creates SDK 57 projects. If your team relies on Expo Go for day-to-day work, the store update will quietly force the question. Its advice is the same as Expo's: a production app should be on development builds, not Expo Go. Make that switch first, and the timing of the store release stops mattering. What you get for the effort. The upgrade is not only defensive. Expo reports that prebuilt expo-modules-core libraries roughly halved a clean Android debug build in its own test, from about 80 to about 39 seconds, with larger savings on CI runners. The fingerprint default now ignores routine changes such as bumping the app version, so you trigger fewer unnecessary native rebuilds. There are also Android home screen widgets in expo-widgets, document scanning in expo-camera, and an alpha expo-app-intents package for Siri and Shortcuts. For founders, the faster CI and fewer rebuilds matter more than any single feature. They shorten the loop between a bug report and a fix in a customer's hands. How Code Flamme would schedule it. Week one: upgrade on a branch, run expo-doctor, regenerate native folders, and list every failure by native module. Week two: fix TypeScript and removed APIs, then test life cycle paths and an Android release build on real devices. Week three: ship to internal testers through your normal channel and watch crash reporting before a store release. Pair it with the rest of your platform calendar. React Native 0.88 changes the support window for older versions, which Code Flamme covered in its React Native 0.88 upgrade cadence post. SDK 58 tooling also requires Node.js 22.13 or newer on the 22 line, 24.3 or newer on the 24 line, or Node.js 26, so CI runners may need attention too. Its Node.js 26 LTS upgrade plan covers the backend side. If your app has years of AppDelegate customisation or a closed-source SDK that has not said anything about UIScene, budget extra time for that alone. It is usually the one item that decides whether the upgrade takes two weeks or six.

Expo ships expo-app-intents: Siri, Shortcuts, Spotlight, and Apple Intelligence for Expo apps. Expo announced expo-app-intents on 19 October 2026, a new alpha package that bridges Apple's App Intents framework into Expo apps, so JavaScript handlers can respond to Siri, Shortcuts, Spotlight search, and Apple Intelligence without writing a separate native target by hand - exactly the kind of platform-integration work that makes partnering with an AI integration team like YuSMP Group worth it once "add an AI assistant surface" shows up on a product roadmap. What expo-app-intents actually does. The package lets an Expo app expose its actions and content to four Apple surfaces at once: Siri voice commands, the Shortcuts app, Spotlight search results, and the on-device context Apple Intelligence uses to reason about what's currently on screen. Developers declare intents in Swift using Expo's inline-modules mechanism - small Swift files living in an app-intents directory inside the project - so Xcode can discover them in the app target at build time, the same way a fully native app would register App Intents. The package then routes invocations from the system back into JavaScript, storing pending calls natively so a Siri request fired while the JS runtime is still cold isn't lost before the bridge is ready. Setup starts with npx expo-app-intents init, which scaffolds the Swift side of the integration. The library requires a development build rather than Expo Go - App Intents has to be compiled into the app target - and needs iOS 16.4 as a baseline, with some capabilities (the deeper Apple Intelligence context hooks) gated behind iOS 18 or iOS 27 and Xcode 27. Why this lands now, not a year ago. App Intents itself isn't new - Apple shipped the framework in 2023 - but it has stayed almost entirely out of reach for Expo and React Native teams because declaring an intent means writing genuine Swift that the compiler can see at build time, something the JS-first Expo workflow was never set up to do cleanly. expo-app-intents is Expo's answer to that gap: keep the actual business logic in JavaScript, where the rest of the app already lives, and generate just enough native Swift scaffolding to satisfy what Xcode requires. It ships as the same release window as Expo SDK 58, which targets iOS 27 and ships on React Native 0.88 - the platform alignment is deliberate, not incidental. Where this actually gets used. * Siri shortcuts for core actions - "reorder my last delivery," "start a workout," "check my balance" - without a parallel native rewrite of the action. * Spotlight-indexed content so in-app items (a saved recipe, a draft, a product) surface in system-wide search the way native-app content already does. * Apple Intelligence context - letting the OS reason about what's on screen in an Expo app the same way it does in a fully native one, which matters for any product betting on on-device AI features as a differentiator. The package is explicitly alpha, and the Swift-authoring requirement means it isn't a one-line install for a team with zero native-iOS familiarity on staff. But it closes a gap that previously forced a hard choice: stay JS-only and skip Apple's assistant surfaces entirely, or eject into a bare workflow just to get App Intents working. For products where "does it talk to Siri" or "does it show up when the user asks Apple Intelligence a question" is a real feature requirement rather than a nice-to-have, that choice no longer has to be made this early.