New Architecture (RN 0.81 / Expo SDK 54): missing shadowNodeFromValue causes iOS Fabric build failure

[jj-devs]

Description

When building with Expo SDK 54 (React Native 0.81.4) + New Architecture enabled, the iOS build fails in the RNGestureHandler Fabric module. shadowNodeFromValue is undefined because REACT_NATIVE_MINOR_VERSION is not defined, so the iOS helper never compiles. As a result Fastlane/Xcode exits with:

• use of undeclared identifier 'shadowNodeFromValue'; did you mean 'shadowNodeListFromValue'?
• no member named 'getTraits' in 'std::vector<std::shared_ptr>'
• 'std::vector<std::shared_ptr>' is not polymorphic

Environment

• Expo SDK 54.0.12
• React Native 0.81.4
• react-native-gesture-handler 2.25.0
• react-native-reanimated 4.1.2
• iOS build via EAS (fastlane)
• RCT_NEW_ARCH_ENABLED=1 / EXPO_NEW_ARCH_ENABLED=1

Expected Result

Build succeeds with RNGestureHandler + Fabric under the New Architecture.

Actual Result

Build fails at “Install pods” / “Run fastlane” with the compiler errors listed above.

Workaround

Adding both a fallback for REACT_NATIVE_MINOR_VERSION and a local shadowNodeFromValue helper fixes the build. The minimal change we use today:

// [cpp-adapter.cpp](http://_vscodecontentref_/0)  (same idea in iOS functions.mm)

#ifndef REACT_NATIVE_MINOR_VERSION
#define REACT_NATIVE_MINOR_VERSION 81
#endif

#include <react/renderer/bridging/Bridging.h>

#if REACT_NATIVE_MINOR_VERSION >= 81
static inline std::shared_ptr<const ShadowNode> shadowNodeFromValue(
        jsi::Runtime &runtime,
        const jsi::Value &shadowNodeWrapper) {
    return Bridging<std::shared_ptr<const ShadowNode>>::fromJs(runtime, shadowNodeWrapper);
}
#endif

Steps to reproduce

1. npx create-expo-app --template expo-template-blank@54 expo-rngh-new-arch
2. cd expo-rngh-new-arch
3. npm install react-native-gesture-handler@2.25.0 react-native-reanimated@4.1.2
4. Enable new architecture
   • app.json → "expo": { "newArchEnabled": true, "ios": { "newArchEnabled": true } }
   • eas.json → "env": { "RCT_NEW_ARCH_ENABLED": "1", "EXPO_NEW_ARCH_ENABLED": "1" }
5. eas build --platform ios --profile production

Expected Result

Build succeeds with RNGestureHandler + Fabric under the New Architecture.

Actual Result

Build fails at “Install pods” / “Run fastlane” with the compiler errors listed above.

Workaround

Adding both a fallback for REACT_NATIVE_MINOR_VERSION and a local shadowNodeFromValue helper fixes the build. The minimal change we use today:

// [cpp-adapter.cpp](http://_vscodecontentref_/0)  (same idea in iOS functions.mm)

#ifndef REACT_NATIVE_MINOR_VERSION
#define REACT_NATIVE_MINOR_VERSION 81
#endif

#include <react/renderer/bridging/Bridging.h>

#if REACT_NATIVE_MINOR_VERSION >= 81
static inline std::shared_ptr<const ShadowNode> shadowNodeFromValue(
        jsi::Runtime &runtime,
        const jsi::Value &shadowNodeWrapper) {
    return Bridging<std::shared_ptr<const ShadowNode>>::fromJs(runtime, shadowNodeWrapper);
}
#endif

A link to a Gist, an Expo Snack or a link to a repository based on this template that reproduces the bug.

https://gist.github.com/jj-devs/d204fbd5c3c8807fd2c8febd200cb34d

Gesture Handler version

2.25.0

React Native version

0.81.4

Platforms

iOS

JavaScript runtime

Hermes

Workflow

Using Expo Prebuild or an Expo development build

Architecture

New Architecture (Fabric)

Build type

Release mode

Device

None

Device model

N/A – occurs on Expo EAS build infrastructure

Acknowledgements

Yes

[m-bert]

Hi @jj-devs! Does this also happen when you locally build your application, or only on EAS?

[jj-devs]

It happens both on EAS and on a local build.

To double‑check, I ran the app locally with the same configuration:
expo prebuild RCT_NEW_ARCH_ENABLED=1 EXPO_NEW_ARCH_ENABLED=1 npx expo run:ios --configuration Release

(or by opening the generated Xcode workspace and pressing Run).

Xcode stops with the exact same compiler errors:

use of undeclared identifier 'shadowNodeFromValue'; did you mean 'shadowNodeListFromValue'?
no member named 'getTraits' in 'std::vector<std::shared_ptr<const facebook::react::ShadowNode>>'
'std::vector<std::shared_ptr<const facebook::react::ShadowNode>>' is not polymorphic

After applying the fallback #define REACT_NATIVE_MINOR_VERSION 81 and the local shadowNodeFromValue helper, the local build succeeds.

[m-bert]

Hi, just to confirm, which version of react-native-gesture-handler do you use? Is that 2.25.0?

[jj-devs]

Yes, the project is on react-native-gesture-handler 2.25.0. That’s the version Expo SDK 54 still installs by default (expo install maps to ~2.25.0), so we kept it to stay on the officially supported matrix for Expo managed/EAS builds. I’m planning to test 2.28.0 separately once Expo publishes compatibility guidance, but the crash reported above happens on the stock SDK 54 setup with 2.25.0.

[m-bert]

Yes, the project is on react-native-gesture-handler 2.25.0.

So yes, that won't work. As far as I remember fix for this was introduced along with RN 0.81 support, so in 2.28.0. You should try to use this version instead (expecially on Expo SDK 54).

For now I'll close this issue, let me know if you still have this issue after update - then I'll reopen it.

That’s the version Expo SDK 54 still installs by default (expo install maps to ~2.25.0)

That's strange, Expo SDK 54 should install 2.28.0 by default. I've just created new expo app and it did install 2.28.0. I'll ask expo team if they know anything about this.

[jakex7]

Hey @jj-devs,
react-native-gesture-handler@~2.28.0 is the recommended version for Expo SDK 54. Could you run npx expo install --check and verify if it recommends you the correct version? If not, could you paste the output of the npx expo-doctor@latest?

[jj-devs]

UPDATE - RESOLVED: After properly configuring the project for CNG/Prebuild workflow, the build with react-native-gesture-handler@2.28.0 + New Architecture now succeeds on EAS Build without requiring any patches.

What was the issue?

The original problem occurred because my project had both native folders (/ios, /android) committed to git AND prebuild configuration in app.json. This created a conflict where EAS Build wasn't properly applying the Expo SDK 54 configuration during the build process.

What changed to fix it:

1. Removed react-native-gesture-handler from exclusions:

   • Removed "react-native-gesture-handler" from expo.doctor.expoSdkVersionCheck.ignore
   • This allowed Expo to properly manage the version

2. Expo automatically installed 2.28.0:

   • When I ran npx expo install --check, it automatically recommended and installed ~2.28.0
   • This confirms that 2.28.0 is indeed the correct version for Expo SDK 54

3. Configured proper CNG/Prebuild workflow:

   • Added /ios and /android to .gitignore
   • Removed native folders from repository
   • Let EAS Build generate native code via expo prebuild

4. Cleaned up configuration:

   • Added expo-system-ui for userInterfaceStyle support
   • Fixed deprecated newArchEnabled warnings

Test Results:

✅ EAS Build: PASSED with react-native-gesture-handler@~2.28.0 + New Architecture
✅ Build ID: 0f3ec143-00d0-46da-9aaa-a1552b877ad8
✅ Configuration: Expo SDK 54, RN 0.81.4, New Architecture enabled
✅ Artifact: Successfully generated and deployed to App Store

Current working configuration:

{
  "dependencies": {
    "react-native-gesture-handler": "~2.28.0"
  },
  "expo": {
    "doctor": {
      "expoSdkVersionCheck": {
        "ignore": []
      }
    }
  }
}