Expo SDK 58 builds now work on Ubriot
Ubriot builds Expo SDK 58 apps for iOS and Android, choosing Xcode 26.4+ and Node 22.13+ per build. What we tested and what to check when you upgrade.
Expo SDK 58 moves to React Native 0.88 and needs Xcode 26.4 or newer and Node.js 22.13 or newer. Ubriot now detects SDK 58 projects and picks the right Xcode and Node.js for each build on workers that have them, so apps still on older SDKs keep building on the same machines with their own toolchain. A self-hosted worker that is missing one stops before installing dependencies and names what to install.
What we tested before saying so
We did not flip the switch on detection alone. We built real SDK 58 apps through Ubriot first: two iOS apps, both uploaded to TestFlight and marked valid by App Store Connect, and an Android release bundle. Over-the-air updates on SDK 58, bare React Native 0.88 apps and Google Play submission are the next things we will verify, and we will update this post and the docs when they are.
What to check when you upgrade
React Native 0.88 removed old bridge APIs, so a native module that still uses RCTCxxBridge fails to compile on iOS. In our case it was a base64 package nothing imported any more; removing it fixed the build. Check your native dependencies for updates before you upgrade.
Separately, and not caused by SDK 58: if your app lives in a monorepo, make sure every package it needs is reachable from the build. We found three ways a scoped build copy can miss one, and wrote them up in their own post.
Three ways a scoped monorepo build copy came up short
Expo SDK 58 on Ubriot: requirements, OTA runtime versions and common fixes