[iOS] Crash on React Native 0.77 - Context Menu View x RNIBaseView

[delphinebugner]

Hi!

Thanks for working on the lib; I'm updating my app from React Native 0.76 to React Native 0.77, and it crashes because of react-native-ios-context-menu and reat-native-ios-utilities

First opened an issue on Zeego's repo: nandorojo/zeego#141 (comment)

But it's the Context Menu View only that crashes with this stack trace:

0   CoreFoundation                	       0x1804b70e0 __exceptionPreprocess + 160
1   libobjc.A.dylib               	       0x18008ede8 objc_exception_throw + 72
2   CoreFoundation                	       0x1804b6c80 -[NSException init] + 0
3   Foundation                    	       0x180eaa40c -[NSObject(NSKeyValueCoding) valueForUndefinedKey:] + 188
4   Foundation                    	       0x180ea92f0 -[NSObject(NSKeyValueCoding) valueForKey:] + 260
5   App.debug.dylib                 0x107ca2e10 __49-[RCTComponentData createPropBlock:isShadowView:]_block_invoke_2.45 + 316 (RCTComponentData.mm:341)
6   App.debug.dylib           	       0x107ca367c __49-[RCTComponentData propBlockForKey:isShadowView:]_block_invoke_2 + 52 (RCTComponentData.mm:367)
7   App.debug.dylib           	       0x107d0a628 RCTPerformBlockWithLogFunction + 408 (RCTLog.mm:167)

Error message is "Error setting onMenuWillShow of RNIContextMenuButton"

Context Menu crashes because valueForUndefinedKey can't be found for props key reactEventHandler for a RCTView -> should it call RNIBaseView+KVC here?

See the (roughly) explaining screenshots:

It looks really close to the code written in this PR: #11, so @coolsoftwaretyler if you have an opinion on this, as author of the RNIBaseView+KVC change !

Disclaimer: I'm a newbie concerning ObjectiveC code 😅

Tried to build a repro but it works fine on an empty project, only fails on my app :/

[delphinebugner]

Also:

• I'm in New Arch
• i'm not using dynamic frameworks
• The error message when using a simple Context Menu View is a different than when I used Zeego, but similar: "Error setting property onDidSetViewID of RNIWrapperView"

[coolsoftwaretyler]

Just stepped away from my computer a few days but if no one else gets to this before I do, I'll take a look soon!

[coolsoftwaretyler]

@delphinebugner - I know you said you can't get a repro to work, and I assume you can't share your full codebase, but is there ay chance you can share an example of your Zeego usage? I want to see if I can make a reproduction on my end. It would be helpful to see what your Zeego usage looks like.

[delphinebugner]

Both my implementation, Zeego's example and simple Context Menu View have the crash; so i think it comes from my app's setup.
I'm in a pnpm monorepo; I use NativeWind, Reanimated, Gesture Handler... I build my repro adding them one by one to a blank template, currently still not able to provoque the crash 🙁 must continue to search!

[delphinebugner]

Update: I just come back to this; tried with react-native-ios-utilities: 5.1.3 and I still have the issue!

Will look more into it now 👀

[delphinebugner]

I tried removing a lot of dependancies and config in my app - nothing changed.

Turns out it's the monorepo itself that causes the pb: we use pnpm + node-linker: isolated
This goes against the recommandation for monorepo: React Native works better with node-linker=hoisted.
But we can't have it on my project.
The result is all of our node_modules subfolders are symlinks.

This causes the crash. When I manually copy (yes, this is shady) the react-native-ios-context-menu and react-native-ios-utilities folders in my node modules, it works.

Recap illustrated here:

@dominicstop @coolsoftwaretyler do you have idea on how to make it work natively ? there's confusion in headers / import files because of the symlinks, definitely; I worked on a repro with pnpm, but can't have it work with node-linker: isolated yet -_-

[dominicstop]

hello @delphinebugner

thank you for the detailed issue, and sorry for the late response! (i am unable to do OSS atm but i'll do my best to help)

i upgraded the example from v75 to v77 but i am unable to repro (see attached video)

Simulator.Screen.Recording.-.iPhone.16.-.2025-04-02.at.01.04.54.mp4

can you please do the ff:

• run bundle exec pod install and paste the output?
• paste the contents of: ios/build/generated/ios/RCTThirdPartyComponentsProvider.mm
• paste your AppDelegate.mm or AppDelegate.swift
• run yarn run react-native info and paste the output

in the meantime, i'll take a look at the info you've provided to see if there's anything i've missed...

[delphinebugner]

Yes, it works with a normal RN 0.77 setup; I reproduce only in a pnpm monorepo with node-linker: isolated - a small repro of it is in progress 🙂

[delphinebugner]

I have the repro!!!!! So happy, I'd never managed to have it before on a showable repo!

Just clone it from here: https://github.com/delphinebugner/expo-monorepo-example

I hope you'll find all your answers in it 🙂

[delphinebugner]

Nit: is probably similar to this issue on React Native Screen -> software-mansion/react-native-screens#2718

Something changed in the way React Native 0.77 link native dep!

[icodesign]

I got the same crash. My investigation indicated that this may be related to dynamic linking.

[
    "expo-build-properties",
    {
      "ios": {
        "deploymentTarget": "17.0",
        "useFrameworks": "dynamic"
      }
    }
]

I was testing using expo default template with the following dependency. If I enabled dynamic use_frameworks in cocoapods, this will crash. However, I'm not sure if it's related to which dependency.

"react-native-ios-context-menu": "3.1.0",
"react-native-ios-utilities": "5.1.2",
"react-native-reanimated": "~3.16.1",

[zhm]

I can also confirm in my setup that the crash only happens when using a symlink'd pnpm monorepo.

When I add node-linker=hoisted to .npmrc in the workspace root, it works without changing anything else. I did a full clean and reinstall/rebuild of everything testing it to verify it.

[coolsoftwaretyler]

When I add node-linker=hoisted to .npmrc in the workspace root, it works without changing anything else. I did a full clean and reinstall/rebuild of everything testing it to verify it.

If this is the root cause for @delphinebugner and @icodesign - I don't think there's much that react-native-ios-utilities needs to change. Expo has this setting documented in their monorepo instructions.

@delphinebugner - I'm trying to check if node-linker=hoisted works on your reproducer app, but I'm getting a totally different error on a clean build:

Seems unrelated to this issue at hand. Any chance you can try node-linker=hoisted and report back?

Interestingly: I ran npx expo install --fix on your reproducer (after removing the ignore block in apps/example/package.json) and then everything worked fine on pnpm build:ios. Of course, that downgrades back to React Native 0.76.9 :/

[zhm]

Thanks for the info @coolsoftwaretyler!

I just cloned the @delphinebugner's reproducer app and I was able to reproduce the error. And then deleted all the intermediate files and replaced node-linker=isolated with node-linker=hoisted and it works correctly.

I know the expo docs do mentioned using hoisted, but support for symlink'd dependencies was turned on by default in RN 0.73. I wonder if the docs just need to be updated? In my app I have many of the common community packages installed and they all work fine inside a symlinked pnpm monorepo. Only this package seems to be impacted, which is weird.

[coolsoftwaretyler]

I still can't get the reproducer past the (maybe) unrelated error, so I'm not sure if I can be super helpful. I tried after clearing my pod cache and it's still got the same runtime not ready error. Still no luck :/