Oliver Edis

ViroReact 3.2.0: Expo SDK 58, React Native 0.88 and Physics on the Web

ViroReact 3.2.0: React Native 0.88 and Expo SDK 58, physics on the web, gestures on phones and leaner Quest builds

Last week's 3.1.0 was about making your apps understand the room they're in. 3.2.0 is about keeping you current. It moves ViroReact onto React Native 0.88 and Expo SDK 58, and picks up a solid batch of improvements for the web, gestures, Quest and audio along the way.

One thing up front: this is a breaking release. ViroReact 3.2.0 needs React Native 0.88 and Expo SDK 58. If you're not ready to make that jump yet, stay on 3.1.x. You keep everything from Advanced VPS to hand occlusion on Quest, and you can upgrade when it suits you.

Up to date with React Native 0.88 and Expo SDK 58

  • React Native 0.88, Expo SDK 58 and React 19.3. ViroReact now tracks the latest stack, so you can pick up everything the React Native and Expo teams have shipped.
  • Rebuilt native renderer. The iOS and Android binaries are rebuilt on ViroCore 3.2.0.
  • visionOS moves too. Vision Pro apps now build on React Native 0.88 with a fresh visionOS template, and our Expo plugin's visionOS patches have been regenerated for SDK 58. That also fixes three patches that failed to apply on SDK 57.

Physics and scene navigation on the web

Our web renderer keeps closing the gap with native. With @reactvision/viro-web-renderer 1.1.1:

  • Physics runs in the browser. The same physics bodies you use on iOS and Android now work on the web, with gravity defaulting to -9.81 unless you set physicsWorld.gravity.
  • Scene navigation works. push, replace, jump, pop and popN all work in ViroARSceneNavigator, so multi-scene experiences behave the same everywhere.
  • Clicks behave like you'd expect. Tapping a child that has no onClick now passes the click up to the nearest parent that does.
  • No more jumping objects. Changing an object's opacity or visibility no longer resets its position.

Pinch, rotate and drag on phones

ViroController's onDrag, onPinch and onRotate now fire on iOS and Android. Pinch and rotate come from the touch screen, so they're a phone gesture (Quest controllers don't send them).

If you already set onPinch or onRotate on a ViroController, those handlers will start firing after you upgrade, so give that logic a quick check.

Leaner Meta Quest builds

  • No ARCore where you don't need it. If your app's xRMode is set to Quest or VR only (no AR), the Expo plugin now leaves ARCore out of the build. In those builds isARSupportedOnDevice returns UNSUPPORTED.
  • Navigation props on Quest. Scenes in ViroXRSceneNavigator now receive arSceneNavigator and live viroAppProps, so code that reads props.arSceneNavigator.viroAppProps works on Quest instead of throwing.

Fixes worth knowing about

  • Sound on iOS. ViroSound.preloadSounds and playing sounds by name work again, and ViroSpatialSound and ViroSoundField no longer crash on mount.
  • Object detection on iPad. ViroObjectDetector results line up correctly in resized and multitasking windows.
  • Your alert labels. Alerts in ReactVision Editor scenes rendered with StudioSceneNavigator now show the button label you set, instead of always saying OK.
  • TypeScript tidy-up. ViroNativeRef is now HostInstance | null. If you call the same methods you don't need to change anything, but if your own types reference NativeMethods, update them. ViroCommonProps also no longer includes ViewProps.onClick.

Upgrade today

Upgrade to Expo SDK 58 first using Expo's upgrade guide, then:

npm install @reactvision/react-viro@3.2.0
npx expo prebuild --clean

Then rebuild your native app. If you ship to the web, update @reactvision/viro-web-renderer to 1.1.1 as well.

Building for Vision Pro? Your existing visionOS folder was generated for React Native 0.86 and won't build against 0.88, so regenerate it:

npx @react-native-community/cli@latest init MyApp \
  --template @reactvision/visionos-template@0.88.1 \
  --directory visionos --skip-install

The full step-by-step is in the Upgrading to 3.2.0 guide.

Or let your coding agent do it: point it at the ViroReact MCP server and ask it what changed since your version.

As always, tell us what you're building, and what you'd like to see next.

Get the ReactVision newsletter

Product announcements, including ViroReact, ReactVision Spatial, Editor and MCP updates, direct to your inbox. No spam, and you can unsubscribe at any time.

Subscribe