wix / wix/react-native-navigation
ReactNativeNavigation.h file not found after updating react native version
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 13.2k
- Forks
- 2.6k
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 1
Description
What happened?
I've been tasked and I am working on updating the react native version of my application. After updating it all and making sure there are no other errors, when trying to build the app for iOS I am getting 'ReactNativeNavigation/ReactNativeNavigation.h' file not found in AppDelegate.m
I've looked around the github issues here and tried changing the podfile as suggested, but to no avail.
Heres the podfile:
# Resolve script with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
"require.resolve(
'#{script}',
{paths: [process.argv[1]]},
)", __dir__]).strip
end
#Use it to require both react-native's and this package's scripts:
node_require('react-native/scripts/react_native_pods.rb')
node_require('react-native-permissions/scripts/setup.rb')
platform :ios, '18.0'
prepare_react_native_project!
setup_permissions([
'AppTrackingTransparency',
# 'Bluetooth',
# 'Calendars',
# 'CalendarsWriteOnly',
'Camera',
# 'Contacts',
# 'FaceID',
# 'LocationAccuracy',
# 'LocationAlways',
# 'LocationWhenInUse',
'MediaLibrary',
'Microphone',
# 'Motion',
'Notifications',
'PhotoLibrary',
# 'PhotoLibraryAddOnly',
# 'Reminders',
# 'Siri',
# 'SpeechRecognition',
# 'StoreKit',
])
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
static_frameworks = [
'FirebaseCore',
'FirebaseCoreExtension',
'GoogleUtilities',
'FirebaseCoreInternal',
'FirebaseInstallations',
'GoogleDataTransport',
'FirebaseFirestoreInternal',
'FirebaseMessagingInternal',
'FirebaseAuth',
]
pre_install do |installer|
installer.pod_targets.each do |pod|
if static_frameworks.include?(pod.name)
puts "Configuring #{pod.name} as static framework"
def pod.build_type
Pod::BuildType.new(:linkage => :static, :packaging => :framework)
end
end
end
end
target 'myapp' do
config = use_native_modules!
$RNFirebaseAsStaticFramework = true
pod 'GoogleAnalytics'
pod 'FirebaseDatabase', :modular_headers => true
pod 'FirebaseABTesting', :modular_headers => true
pod 'FirebaseAppCheckInterop', :modular_headers => true
pod 'leveldb-library', :modular_headers => true
pod 'nanopb', :modular_headers => true
config = use_native_modules!
use_react_native!(
:path => config[:reactNativePath],
:hermes_enabled => true,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
post_install do |installer|
# https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
react_native_post_install(
installer,
config[:reactNativePath],
:mac_catalyst_enabled => false,
# :ccache_enabled => true
)
end
end
What was the expected behaviour?
That the app correctly builds for iOS.
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!
Started happening after updating from react-native 0.74.3 to 0.78
In what environment did this happen?
React Native Navigation version: 8.7.5
React Native version: 0.78
Has Fabric (React Native's new rendering system) enabled: (yes/no) No
Node version: 18.20.8
Device model: iPhone 17 Pro (emulator)
iOS version: 26.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the iOS build failure and inspect the AppDelegate.m import together with the Podfile configuration. Compare the React Native 0.74.3 and 0.78 integration points mentioned in the report; done means the ReactNativeNavigation header resolves and the app builds successfully for iOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100