Skip to content

feat: build Expo SDK 56 apps - #42

Open
WillyAntunez wants to merge 28 commits into
mainfrom
feature/expo-sdk-56
Open

WillyAntunez wants to merge 28 commits into
mainfrom
feature/expo-sdk-56

Conversation

@WillyAntunez

Copy link
Copy Markdown
Owner

Build Expo SDK 56 apps

rn-xtool build now builds Expo SDK 56 apps (expo 56.0.24 or newer 56.x, react-native 0.85.3) on Linux, on the same route as SDK 57: the vendored Expo plugin, the vendored React Native scripts, React Native 0.85.3's adapted artifacts and the jsi step before rn-spm. A fresh default@sdk-56 template with expo-dev-client builds cold and warm with no hand fix. SDK 55 and older are refused with a message that names the supported SDKs, and a build killed halfway no longer leaves the next builds failing without an explanation.

Design: docs/design/specs/2026-11-11-expo-sdk-56-design.md. Plan: docs/design/plans/2026-11-11-expo-sdk-56.md.

Status: SDK 56 is build-verified; the device pass is pending.

  • Device pass on the SDK 56 default template (dev client, expo-router navigation, reanimated, expo-image, Fast Refresh)
  • Owner's SDK 56 app

What changed

  • The SDK 56 line and its gate. SDK 56's set is a floor (expo 56.0.24, expo-modules-core 56.0.27, expo-modules-jsi 56.0.14, expo-modules-autolinking 56.0.24, expo-file-system 56.0.11, expo-font 56.0.7, each on SDK 56's line; react-native exactly 0.85.3). Below it the build stops with the remedy; a newer 56.x builds with the ⚠ Newer than the Expo SDK 56 set … line. doctor --project names the SDK and the verified versions.
  • The jsi patch and a readable interface. expo-modules-jsi+56.0.14.patch (SDK 56 only) makes expo.CppError's message internal so Swift 6.4 compiles it, and marks four conformances to the internal JSIRepresentable @_spi(Internal), as jsi 57.1.3 does, so Swift 6.4 writes an ExpoModulesJSI.swiftinterface every module can import. On SDK 56 and 57 the jsi step reads the interface it built and stops at once on a line no Swift compiler parses, instead of minutes later in xtool-build.
  • JSI headers in either layout. The jsi step takes NativeState.h and the headers it includes from include/Public (jsi 57 and newer) or include (jsi 56), and names the missing header when one is not there.
  • iOS floor from podspecs. The vendored plugin gives each generated Expo package the highest of its spm.config.json floor, its podspec's iOS deployment target and core's, capped at the App target's iOS 16.4. A podspec that asks for more prints one ⚠ line naming the package, the iOS version it asks for and the availability check its newer code needs.
  • The autolinking-based gate for expo-file-system and expo-font. On SDK 56 and 58, and in hybrid apps (bare React Native with Expo modules) on SDK 58, the version check reads these two packages where expo-modules-autolinking links them, as its own CLI answers. A package the app excludes is skipped; one installed but not linked, and not excluded, stops the check with the remedy. When the CLI cannot be asked, the check reads node_modules by a fixed rule and says so in one ⚠ line that names the reason.
  • Interrupted-build recovery. A build killed during jsi or xtool-build leaves a module cache clang cannot read. build --clean removes the jsi build's scratch on every kind, and a failure on such a file adds a paragraph naming the folder and the remedy, at build, install and install --network. On an Expo project build --clean keeps ios-xtool/.build, so the paragraph for that folder names rm -rf ios-xtool/.build. The jsi and xtool-build output now goes through a pipe, so SwiftPM prints each progress update on its own line.
  • Drift watch and docs. The daily drift watch checks expo-56/default, and the weekly exploration covers SDK 54 and 55. README, how-it-works (SDK 56 reference timings included), recipe, libraries, bare-react-native, troubleshooting, RELEASING and the vendored plugin's README cover SDK 56 and hybrid apps where they apply.

On the SDK 56 template, ios.icon is an Icon Composer icon, which needs Xcode's actool, so the app has no icon until ios.icon is a PNG; and ExpoModulesWorkletsAdapter is left out because ExpoModulesCore is precompiled, while ExpoModulesWorklets.framework is embedded.

Verification

  • SDK 56 default template (fresh default@sdk-56 + expo-dev-client, 2026-11-11): build --clean 346 s cold (xtool-build 223 s), build 65 s warm (xtool-build 38 s); App.app 140 MB with 14 frameworks (ExpoImage, SDWebImage and its coders, libavif included). The generated interface has 570 lines and none that fails to parse; all 21 generated Expo packages declare iOS 16.4; the interface stamp is unchanged by the warm build.
  • SDK 57 (build --clean): 82 s, App.app 94 MB with 8 frameworks; the headers tree and the interface guard pass.
  • SDK 58 (build --clean): about 313 s, App.app 151 MB with 14 frameworks.
  • Bare React Native 0.85 (build --clean): about 215 s, App.app 86 MB with 3 frameworks.
  • Symbol check by hand of the embedded frameworks' imports from each other (all of them; on SDK 57 the four Expo ones): SDK 56 967 symbols over 19 framework pairs, SDK 57 707 over 10, SDK 58 1174 over 23, bare 0.85 119 over 2; 0 missing in each. rn-xtool's own frameworks check passed on all four.
  • Interrupted builds, reproduced: a module cache file cut to 0 bytes under the jsi scratch stops build with the jsi paragraph, and build --clean gets through the jsi step again; one under ios-xtool/.build stops xtool-build with its paragraph, and rm -rf ios-xtool/.build then build succeeds with a cold xtool-build.
  • npm test: 2984 passed, 6 skipped. npm run lint, npm run check:mentions and npm run scan:private are clean.

Merge gate

  • CI green.
  • The two device checks above.

Notes for the changelog

  • Every entry sits under [Unreleased] (Added, Changed, Fixed); this PR makes no release and bumps no version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant