do not install folly manually if prebuilt RN deps are used

[fobos531]

Hello @dominicstop - starting from React Native 0.80, there is an ability to use prebuilt RN dependencies. See: https://reactnative.dev/blog/2025/06/12/react-native-0.80#experimental---react-native-ios-dependencies-are-now-prebuilt When this is done, libraries that configure Folly manually clash with this approach, resulting in build errors. Since this library configures Folly manually, we need to account for this.

Would you be able to check this PR out?

[JustJoostNL]

Just landed on this issue myself:

⚠️  Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: Unable to find a specification for `RCT-Folly (= 2022.05.16.00)` depended upon by `react-native-ios-utilities`

You have either:
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.


pod install --repo-update --ansi exited with non-zero code: 1

[IsaacInsoll]

This is the only thing blocking me from expo@beta upgrade :)

[rrebase]

I can confirm this patch is needed to build with latest Expo SDK 54 Beta using RN 0.81.0.

In addition to this I also had to patch a few react/utils/FollyConvert.h imports in react-native-ios-utilities similar to https://github.com/rnmapbox/maps/pull/3937/files

[nandorojo]

Hi all, just merged it. Dominic is taking a break from open source at the moment, so I'm going to ask if I can get NPM publish access 🙂

The best approach would be to add a CI script to the package which publishes to NPM on merging to main. Any help on that would be greatly appreciated. CC @hirbod

[furkananter]

[!] Unable to find a specification for RCT-Folly (= 2022.05.16.00) depended upon by react-native-ios-utilities

You have either:

• mistyped the name or version.
• not added the source repo that hosts the Podspec to your Podfile.

Recently, I attempted to upgrade to SDK54, but the error still persists.

[pablomikel]

A temporary workaround is to disable the precompiled deps with RCT_USE_PREBUILT_RNCORE=0 RCT_USE_RN_DEP=0 during prebuild or run:ios

[ahmed-sudowrite]

@nandorojo any update on when we'll have this on NPM? Thanks!

[nandorojo]

I added this script but it's failing:

https://github.com/dominicstop/react-native-ios-context-menu/actions/runs/17646185609/job/50144627407

If anyone can fix it, it'll publish!

[ahmed-sudowrite]

@nandorojo i think it's because we have react 18 but types installed are for react 19, and rn 0.77 from the examples is forcing react 18? Just upgrading all the reacts to 19 might help since it's required in the newest react native as well afaik

[nandorojo]

Well that's interesting info ^

[mpb700]

Issue resolved yet?

[rash2104]

A temporary workaround is to disable the precompiled deps with RCT_USE_PREBUILT_RNCORE=0 RCT_USE_RN_DEP=0 during prebuild or run:ios

Working thanks a lot

[JustJoostNL]

Any news on an update?

[moekaddour]

Adding env with these two env values in eas.json would solve the issue when running eas build --profile development --platform ios

 "development": {
      "developmentClient": true,
      "distribution": "internal",
      "env": {
        "RCT_USE_PREBUILT_RNCORE": "0",
        "RCT_USE_RN_DEP": "0"
      }

[gustavohariel]

Adding env with these two env values in eas.json would solve the issue when running eas build --profile development --platform ios

 "development": {
      "developmentClient": true,
      "distribution": "internal",
      "env": {
        "RCT_USE_PREBUILT_RNCORE": "0",
        "RCT_USE_RN_DEP": "0"
      }

Thank you for this.

[mrkeyiano]

A temporary workaround is to disable the precompiled deps with RCT_USE_PREBUILT_RNCORE=0 RCT_USE_RN_DEP=0 during prebuild or run:ios

this was the fix, thanks alot

[VGerris]

For expo SDK 53 : react-native-menu/menu#1187 . not the cleanest but may help someone. Suggestions for improvement appreciated.