iOS 27ExpoReact NativeUpgrade Guide

iOS 27 UIScene Requirement: What React Native and Expo Apps Must Change

iOS 27 requires the UIKit scene lifecycle. What it means for React Native and Expo apps, which AppDelegate code breaks, how to migrate and what to test.

DeveloperMill5 min read

Every iOS release brings changes, but iOS 27 has one that stops apps from launching: apps built with the iOS 27 SDK must use the UIKit scene-based life cycle. Apple's migration documentation is explicit that apps which don't adopt it fail to launch.

For React Native and Expo apps, most of the work is handled by the framework. The risk is in the custom code and third-party SDKs that hooked into AppDelegate. Here's what changes, who needs to act, and what to test.

What the scene lifecycle is

Older iOS apps had one UIApplicationDelegate, the AppDelegate, that received every lifecycle event: launch, foreground, background, opened URLs, universal links. Since iOS 13, Apple has supported scenes, one per window, each with its own UISceneDelegate. iPad multitasking, multiple windows and the resizable iPhone apps introduced in iOS 27 are all built on scenes.

UIKit has been logging warnings for apps that haven't migrated since iOS 18.4. With the iOS 27 SDK, the warning becomes a hard requirement.

Who needs to act, and when

  • Apps already in the store that were built with an older SDK keep launching on iOS 27.
  • The requirement applies when you build with the iOS 27 SDK (Xcode 27).
  • Apple has required the latest SDK for new App Store submissions each spring in recent years, so expect to be building with the iOS 27 SDK by around April 2027. Watch App Store Connect announcements for the exact date.

In practice, any app that will ship an update in 2027 needs this migration.

Expo apps: SDK 58 does most of the work

Expo SDK 58 is built for iOS 27 and switches to the scene-based life cycle. Prebuild now generates a SceneDelegate.swift alongside AppDelegate.swift, and Expo's own modules are updated for it. For a typical Expo app using Continuous Native Generation, where native folders are generated by prebuild rather than edited by hand, the upgrade is:

npx expo install expo@^58.0.0 --fix
npx expo-doctor@latest
npx expo prebuild --clean

Then check three things:

  1. Config plugins that modify AppDelegate. If you or a library uses a config plugin to inject code into AppDelegate (deep link handling, attribution, analytics init), that code may now sit in a method that's no longer called. Expo maintains a migration guide at expo.fyi/ios-scene-lifecycle.
  2. Third-party native SDKs. Push, attribution, deep linking, analytics, ads and auth SDKs often hook into AppDelegate. Update each to a version that states scene support. Customer.io's Expo plugin, for example, ships a scene-lifecycle path specifically for SDK 58.
  3. Hard-coded layout. iOS 27 makes iPhone apps resizable. Rely on safe areas and flexible layouts rather than fixed screen dimensions.

Bare React Native apps: the manual migration

Without Expo's prebuild you'll need to add the scene configuration yourself:

  • Add a UIApplicationSceneManifest to Info.plist with a scene configuration that points at your scene delegate class.
  • Create a SceneDelegate that creates the window and hosts the React Native root view in scene(_:willConnectTo:options:).
  • Move event handling out of AppDelegate (see the table below) and forward URLs and user activities to React Native's RCTLinkingManager so the Linking API keeps working.
  • Compare your native files against the React Native template for your version using the React Native Upgrade Helper.

Where AppDelegate code has to move

EventOld AppDelegate methodScene lifecycle
Open a URL (custom scheme, OAuth redirect)application(_:open:options:)scene(_:openURLContexts:)
Universal linkapplication(_:continue:restorationHandler:)scene(_:continue:)
URL or activity that launched the applaunchOptionsconnectionOptions in scene(_:willConnectTo:options:)
Became active / resigned activeapplicationDidBecomeActive / applicationWillResignActivesceneDidBecomeActive / sceneWillResignActive
Background / foregroundapplicationDidEnterBackground / applicationWillEnterForegroundsceneDidEnterBackground / sceneWillEnterForeground
Home screen quick actionapplication(_:performActionFor:completionHandler:)windowScene(_:performActionFor:completionHandler:)
The app's windowAppDelegate.windowThe scene's window

Some things stay in AppDelegate, including push notification token registration (didRegisterForRemoteNotificationsWithDeviceToken) and app-wide setup in didFinishLaunchingWithOptions. Notification taps handled through UNUserNotificationCenter's delegate, which expo-notifications uses, aren't affected by the move. Code that read the notification from launchOptions is.

Also search native code for UIApplication.shared.keyWindow and UIApplication.shared.windows. Both assume a single window, and with scenes they can return the wrong window or nothing at all. That shows up as modals, auth sheets or payment sheets that silently fail to present.

What to test before you ship

Run every case on a real device, starting from a killed app as well as from the background, because cold-start behavior is where the scene migration most often breaks:

  • Custom-scheme deep links and Expo Router deep links
  • Universal links from Messages, Mail and Safari
  • Tapping a push notification (push notifications guide)
  • OAuth and magic-link sign-in redirects
  • In-app purchases and payment sheets presenting correctly
  • Home screen quick actions and widgets that deep link into the app
  • Backgrounding and returning, including AppState-driven logic like session refresh
  • Resizing on iPad and on resizable iPhone windows

Plan it, don't wait for the deadline

The migration is usually a day or two for an Expo app and longer for bare apps with lots of native customization. The expensive version is discovering it in April when a release is blocked. Put it on the roadmap alongside Google Play's API 36 targeting requirement, and budget for yearly changes like these. Our app maintenance cost guide shows how.

Frequently asked questions

Do React Native apps need to adopt UIScene for iOS 27?

Yes, once they're built with the iOS 27 SDK. Apple's documentation says apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch. Expo SDK 58 adopts it automatically. Bare React Native apps need a SceneDelegate added and any AppDelegate customizations moved.

Will my existing app stop working on iOS 27?

Apps already on the App Store that were built with an older SDK keep launching on iOS 27. The requirement applies when you build with the iOS 27 SDK, which you'll have to do once Apple requires it for new submissions.

What breaks when moving to the scene lifecycle?

Code in AppDelegate that handles opening URLs, universal links, quick actions or launch options, or that assumes a single app window, because those events are delivered to the scene delegate instead. Third-party SDKs that hook into AppDelegate or use keyWindow need versions with scene support.

How do I upgrade an Expo app for iOS 27?

Upgrade to Expo SDK 58 with npx expo install expo@^58.0.0 --fix, run npx expo-doctor, update config plugins and native SDKs to scene-compatible versions, and rerun prebuild. Then test deep links, push notification taps and auth redirects from a cold start on a real device.

Talk to a senior React Native team

Book a free 30-minute call. Bring your app, your quote or your deadline, and leave with a clear plan for building, upgrading or maintaining it.

Book a free call