After RN/Xcode upgrade `FirebaseCoreInternal.modulemap' not found` #7207

jinhale · 2023-06-28T19:14:41Z

jinhale
Jun 28, 2023

How can I restore a successful build process?

After manually upgrading from RN version 0.70.2 to RN version 0.72.0 using a new project with code copied from my existing project, the new and existing project will no longer build using Xcode. I'm tying to build according to Any iOS Device (arm64), which normally works. Here is the error:

~/Library/Developer/Xcode/DerivedData/<project-name>-aobgsqdmebtxwebkbxofzpscossc/Build/Intermediates.noindex/<project-name>.build/Debug-iphoneos/<project-name>.build/DerivedSources/<project-name>_vers.c module map file '~/Library/Developer/Xcode/DerivedData/<project-name>-aobgsqdmebtxwebkbxofzpscossc/Build/Products/Debug-iphoneos/FirebaseCoreInternal/FirebaseCoreInternal.modulemap' not found

When I look up modulemap files it seems to be related to manually linking files which is no longer applicable so I'm left confused.

I have added GoogleService-Info.plist and checked to ensure the configuration code for FireBase was retained to the best of my ability.

A similar problem has no accepted solution, but I should mention I have tried the obvious suggestions: close and reopen Xcode, clean before building, changing the minimum iOS Deployment Target, and removing node_modules and Pods/ folder before reinstalling using yarn and pod install.

Here is npx react-native info output:

System: OS: macOS 13.4 CPU: (4) x64 Intel(R) Core(TM) i3-8100B CPU @ 3.60GHz Memory: 183.78 MB / 8.00 GB Shell: version: 3.2.57 path: /bin/bash Binaries: Node: version: 20.3.1 path: /usr/local/bin/node Yarn: version: 1.21.1 path: ~/npm-global/bin/yarn npm: version: 9.6.7 path: /usr/local/bin/npm Watchman: version: 2023.06.12.00 path: /usr/local/bin/watchman Managers: CocoaPods: version: 1.12.1 path: ~/.rvm/gems/ruby-2.7.5/bin/pod SDKs: iOS SDK: Platforms: - DriverKit 22.4 - iOS 16.4 - macOS 13.3 - tvOS 16.4 - watchOS 9.4 Android SDK: Not Found IDEs: Android Studio: Not Found Xcode: version: 14.3.1/14E300c path: /usr/bin/xcodebuild Languages: Java: Not Found Ruby: version: 2.7.5 path: ~/.rvm/rubies/ruby-2.7.5/bin/ruby npmPackages: "@react-native-community/cli": Not Found react: Not Found react-native: Not Found react-native-macos: Not Found npmGlobalPackages: "*react-native*": Not Found Android: hermesEnabled: false newArchEnabled: false iOS: hermesEnabled: true newArchEnabled: false

Here is a snippet of changes to package.json:

"@react-native-firebase/analytics": [-"^16.4.0",-]{+"^18.1.0",+} "@react-native-firebase/app": [-"^16.4.0",-]{+"^18.1.0",+} "@react-native-firebase/messaging": [-"^16.4.0",-]{+"^18.1.0",+}

Answered by jinhale

Feb 2, 2024

In the end I upgraded the OS, and XCode, then I created a new project adding each package one at a time. This worked, but it is a periodic issue with different versions.

View full answer

mikehardy · 2023-06-29T06:00:55Z

mikehardy
Jun 29, 2023
Maintainer

It is generally an intractable problem attempting to slowly tease sufficient information out of a project I can't see in order to figure out why the build won't work.

In place of attempting to do that, I have a fully scripted demonstrator repo that starts with npx react-native init and bit-by-bit adds in everything necessary to successfully build (assuming you have a plist / json file for google services)

I haven't officially promoted the react-native 0.72 version of it but I do testing with the react-native releases working group and I had it working as recently as react-native 0.72.0-rc05 - I don't anticipate anything big needs to change for the final release version: https://github.com/mikehardy/rnfbdemo/blob/rn72/make-demo.sh

Carefully read the comments and examine what the script does, maybe even try it as a scratch pad, it should work

I will note that if there is something related to FirebaseCoreInternal, please make sure you are using use_frameworks! :linkage => :static with no unsupported workarounds. FirebaseCoreInternal is a Swift module and it's linkage is problematic when the workarounds are attempted.

0 replies

anhquan99 · 2023-09-12T15:40:00Z

anhquan99
Sep 12, 2023

I found the solution at facebook/react-native#29605 (comment)

0 replies

jyotiprakash111 · 2023-11-10T05:19:22Z

jyotiprakash111
Nov 10, 2023

Current RN Version 0.70, i am trying to upgrage from - 0.63 to 0.70, i am facing the above error, i have tried everything nothing is working for me as of now.

3 replies

jyotiprakash111 Nov 10, 2023

System:
OS: macOS 14.0
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 571.49 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 18.18.0 - /usr/local/bin/node
Yarn: Not Found
npm: 9.8.1 - /usr/local/bin/npm
Watchman: 2023.09.25.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.12.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0
Android SDK: Not Found
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.10811636
Xcode: 15.0.1/15A507 - /usr/bin/xcodebuild
Languages:
Java: 20.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: ^0.70.0 => 0.70.14
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

mikehardy Nov 10, 2023
Maintainer

Interesting, your cocoapod is out of date (1.14.2) is current but your Java is arguably too new (20? Does that even work? I think 17 is safer at the moment) and react-native 0.70 is old, why not 0.72.6 if you are upgrading things?

There is no problem with this repo though, and we don't have the resources to debug everyone's build problems since they are infinitely variable

Here is a script that works though, and will show you exactly how to do the minimal integration for a successful iOS build, on Xcode 15 etc https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

GrkikyanRobert Mar 5, 2024

cool situation

minhchienwikipedia · 2024-02-02T13:06:33Z

minhchienwikipedia
Feb 2, 2024

@jinhale I'm getting the same issue, do you have a solution?

1 reply

jinhale Feb 2, 2024
Author

In the end I upgraded the OS, and XCode, then I created a new project adding each package one at a time. This worked, but it is a periodic issue with different versions.

Answer selected by jinhale

kailash-sssg · 2024-04-08T10:09:56Z

kailash-sssg
Apr 8, 2024

@jinhale I'm getting the same issue, do you have a solution? Did't find a way to fix it.
having the upgraded OS and XCode which is OS- Sonoma, and XCode - 15.2

0 replies

rehan-taiftec · 2024-04-16T07:30:34Z

rehan-taiftec
Apr 16, 2024

any solution i am getting the same error after upgrading to the latest mac os

1 reply

kailash-sssg Apr 16, 2024

@rehan-taiftec, As of now only solution or workaround that worked for me is went through the way that has been mentioned by @jinhale here #7207 (reply in thread)

minhchienwikipedia · 2024-04-16T10:51:06Z

minhchienwikipedia
Apr 16, 2024

My solution is using use_frameworks! :linkage => :static

3 replies

vedant6565 Apr 25, 2024

on which file write this please mention properly

minhchienwikipedia Apr 26, 2024

on ios/Podfile

muslimmuda15 May 4, 2024

Please, Can you write full the code?

SamDuke99 · 2024-04-29T13:39:21Z

SamDuke99
Apr 29, 2024

This solution works for me:

Go into build settings for your project
Head to architectures
Open up excluded architectures
Exclude 'arm64'

See pic for more context:

0 replies

AteebNoOne · 2024-05-12T03:34:03Z

AteebNoOne
May 12, 2024

/Users/mac/Library/Developer/Xcode/DerivedData/CI_Builders-doiyvzlocwxpabcvsqshiqmtknxx/Build/Intermediates.noindex/CI_Builders.build/Debug-iphonesimulator/CI_Builders.build/DerivedSources/CI_Builders_vers.c module map file '/Users/mac/Library/Developer/Xcode/DerivedData/CI_Builders-doiyvzlocwxpabcvsqshiqmtknxx/Build/Products/Debug-iphonesimulator/FirebaseCoreInternal/FirebaseCoreInternal.modulemap' not found

React native info:

System:
OS: macOS 13.6.6
CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
Memory: 701.54 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 21.7.2
path: /usr/local/bin/node
Yarn: Not Found
npm:
version: 10.5.0
path: /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.15.2
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.2
- iOS 17.2
- macOS 14.2
- tvOS 17.2
- visionOS 1.0
- watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode:
version: 15.2/15C500b
path: /usr/bin/xcodebuild
Languages:
Java: Not Found
Ruby:
version: 3.3.0
path: /usr/local/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.73.6
wanted: 0.73.6
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false

Podfile:

require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip

platform :ios, min_ios_version_supported

prepare_react_native_project!

If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.

because `react-native-flipper` depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`

```js

module.exports = {

dependencies: {

...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),

```

flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled

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

target 'CI_Builders' do
config = use_native_modules!
pod 'Firebase', :modular_headers => true
pod 'FirebaseCoreInternal', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
use_react_native!(
:path => config[:reactNativePath],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
:flipper_configuration => flipper_config,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)

target 'CI_BuildersTests' do
inherit! :complete
# Pods for testing
end

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
)
end
end

is there any solution for it?

0 replies

bilal-prog · 2024-05-17T11:41:10Z

bilal-prog
May 17, 2024

I get that error when I add tvOS to the targets, PLZ is there any solution ?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

After RN/Xcode upgrade `FirebaseCoreInternal.modulemap' not found` #7207

{{title}}

Replies: 10 comments 8 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

After RN/Xcode upgrade FirebaseCoreInternal.modulemap' not found #7207

Replies: 10 comments · 8 replies

mikehardy Jun 29, 2023 Maintainer

mikehardy Nov 10, 2023 Maintainer

jinhale Feb 2, 2024 Author

If you are using a react-native-flipper your iOS build will fail when NO_FLIPPER=1 is set.

because react-native-flipper depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude react-native-flipper using a react-native.config.js

```js

module.exports = {

dependencies: {

...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),

```

is there any solution for it?

After RN/Xcode upgrade `FirebaseCoreInternal.modulemap' not found` #7207

Replies: 10 comments 8 replies

mikehardy
Jun 29, 2023
Maintainer

mikehardy Nov 10, 2023
Maintainer

jinhale Feb 2, 2024
Author

If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.

because `react-native-flipper` depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`