React-native-firebase: Archiving issues iOS => FirebaseCore/FirebaseCore.h' file not found -- only on iOS Release config

Created on 17 Dec 2018  路  12Comments  路  Source: invertase/react-native-firebase

As issues revolving around archiving keep getting closed i want to open a new thread.

i refer to some issues: one of them was :https://github.com/invertase/react-native-firebase/issues/1166

There has been a solution found for this problem.

"Add the correct archive header path to the Release part of both Framework Search Paths and Header Search Paths in the RNFirebase project build settings. This defaults to "$(BUILD_ROOT)/../IntermediateBuildFilesPath/UninstalledProducts/iphoneos" but the location is dependent on your overall project build settings."

This works locally but not if you are working with a remote CI/CD process.

Can you guys please update this to make it work with a remote build process.

Using modular headers in podfile does not work nor can we remove use_frameworks as we use different pods which rely on this

Firestore

Most helpful comment

The workaround mentioned at the 3.2.2 release notes does not work for my project. The problem persists even after adding the Pods framework to the RNFirebase project build phase.

Here is the work around that I use now, in the project Podfile, that works reliably on clean checkout without dependency modifications;

post_install do |installer|
  system("mkdir -p Pods/Headers/Public/FirebaseCore && cp Pods/FirebaseCore/Firebase/Core/Public/* Pods/Headers/Public/FirebaseCore/")
end

All 12 comments

The workaround mentioned at the 3.2.2 release notes does not work for my project. The problem persists even after adding the Pods framework to the RNFirebase project build phase.

Here is the work around that I use now, in the project Podfile, that works reliably on clean checkout without dependency modifications;

post_install do |installer|
  system("mkdir -p Pods/Headers/Public/FirebaseCore && cp Pods/FirebaseCore/Firebase/Core/Public/* Pods/Headers/Public/FirebaseCore/")
end

Please follow the issue template @Benjuari - we have no clue what version you're working with here.

@Ehesp I can confirm this issue is relevant on 5.2.0 (latest at the time of writing). Could you please re-open this?

@bartolkaruza thanks for the support!
@Ehesp I also confirm this! I was working with the latest version.

I was having the same issue on react-native 0.58
The Post install script worked for me 馃憤
I added the script in the post_install script

The workaround mentioned at the 3.2.2 release notes does not work for my project. The problem persists even after adding the Pods framework to the RNFirebase project build phase.

Here is the work around that I use now, in the project Podfile, that works reliably on clean checkout without dependency modifications;

post_install do |installer|
  system("mkdir -p Pods/Headers/Public/FirebaseCore && cp Pods/FirebaseCore/Firebase/Core/Public/* Pods/Headers/Public/FirebaseCore/")
end

@bartolkaruza This works when Archiving but on running on device, I get the Missing Module Error:
in native.js file inside initialiseNativeModule function.

I'm simply trying to listen for Auth change event.
This issue is a blocker for us because another pod library depends on use_framework.
Is there any workaround for this issue?
@Ehesp

@bartolkaruza @Ehesp Any help would be greatly appreciated!

any update, and i don't even have pod file in my project.

Screenshot 2019-04-10 at 5 11 28 PM

and the error is

Screenshot 2019-04-10 at 5 13 06 PM

Hello 馃憢, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

Problem the still exist. Anybody fixed this problem? I can't normal use Gitlab CI.

2163 is the canonical place we are tracking header file problems, and it has a workaround (actually the one listed above - a header copy as Podfile post install step) that works in archive for release mode, including with a reproducible demo that proves it

Hi, I am also face this issue. But I have fixed error. First goto project folder in ios folder and open profile file you just Commit use_framework. Then delete projectName.xcworkspace, pod folders and profile.lock file. And pod update, pod install finally open project to xcode and build. Easy to solve this issue and fixed.

Was this page helpful?
0 / 5 - 0 ratings