iOS - RN0.76 - with RNN v8.0.0 version - Use of undeclared identifier 'RCTAppSetupDefaultJsExecutorFactory, RCTAppSetupDefaultModuleFromClass , RCTLegacyInteropComponents

[manoj-mehra-spraxa]

What happened?

/node_modules/react-native-navigation/lib/ios/RNNAppDelegate.mm:78:12 Use of undeclared identifier 'RCTAppSetupDefaultJsExecutorFactory'

/node_modules/react-native-navigation/lib/ios/RNNAppDelegate.mm:100:12 Use of undeclared identifier 'RCTAppSetupDefaultModuleFromClass'

node_modules/react-native-navigation/lib/ios/RNNAppDelegate.mm:116:40 Use of undeclared identifier 'RCTLegacyInteropComponents

checked with sample app - having same issue

"react": "18.3.1",
"react-native": "0.76.0",
Xcode 16.2

What was the expected behaviour?

build should be created and working with the version

Was it tested on latest react-native-navigation?

• I have tested this issue on the latest react-native-navigation release and it still reproduces.

Help us reproduce this issue!

No response

In what environment did this happen?

React Native Navigation version: 8.0.0
React Native version: "0.76.0",
Has Fabric (React Native's new rendering system) enabled: (yes/no) yes
Node version: v20.9.0
Device model: iphone SE
iOS version:18.3.1

[ee-dd-cc]

same problem.

[d4vidi]

Is this with new architecture enabled? It's still in the works; Not officially support yet.

[manoj-mehra-spraxa]

@d4vidi so if we disable new architecture for iOS RN v0.76 with RNN v8.0.0 - it will work or not ?

[d4vidi]

Should work with new_arch=false. See here: https://github.com/wix/react-native-navigation/releases/tag/8.0.0

[manoj-mehra-spraxa]

@d4vidi ok thanks i will check this soon.

[manoj-mehra-spraxa]

@d4vidi after disable new arch in iOS RN v0.76 - RNN v8.0.0 its working - we will re-enable this when new arch is ready to use with react-native-navigation

[d4vidi]

@d4vidi after disable new arch in iOS RN v0.76 - RNN v8.0.0 its working - we will re-enable this when new arch is ready to use with react-native-navigation

Great. As I mentioned, it's in the works, a few weeks away I believe.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest version and report back. Thank you for your contributions.

[stale]

The issue has been closed for inactivity.