[🐛] 'FirebaseFunctions/FirebaseFunctions-Swift.h' file not found #6382

nicolas-wl · 2022-07-11T23:54:45Z

When building for iOS, I keep getting the following error:

In file included from .../node_modules/@react-native-firebase/storage/ios/RNFBStorage/RNFBStorageModule.m:18:
.../my-app/ios/Pods/Headers/Private/Firebase/Firebase.h:54:13: fatal error: 'FirebaseFunctions/FirebaseFunctions-Swift.h' file not found
    #import <FirebaseFunctions/FirebaseFunctions-Swift.h>

dependencies are all at latest version

    "@react-native-firebase/app": "^15.1.1",
    "@react-native-firebase/auth": "^15.1.1",
    "@react-native-firebase/firestore": "^15.1.1",
    "@react-native-firebase/functions": "^15.1.1",
    "@react-native-firebase/messaging": "^15.1.1",
    "@react-native-firebase/storage": "^15.1.1",

podfile

require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
require_relative '../node_modules/react-native/scripts/react_native_pods'

platform :ios, '12.4'
install! 'cocoapods', :deterministic_uuids => false

target 'MyApp' do
  config = use_native_modules!

  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true
  pod 'FirebaseAppCheckInterop', :modular_headers => true
  pod 'FirebaseAuthInterop', :modular_headers => true
  pod 'FirebaseMessagingInterop', :modular_headers => true
  pod 'GTMSessionFetcher', :modular_headers => true
  pod 'FirebaseStorageInternal', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true
  $RNFirebaseAsStaticFramework = true

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    # to enable hermes on iOS, change `false` to `true` and then install pods
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )
  
target 'MyAppTests' do
inherit! :complete
# Pods for testing
end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable the next line.
  use_flipper!()

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

end

The text was updated successfully, but these errors were encountered:

mikehardy · 2022-07-15T01:21:44Z

🤔 Hmm

I don't recognize these, but I see them show up pretty frequently now that use_frameworks is required. Why are these here? Where does the recommendation to turn them on come from? What problem do they solve, if you cannot build currently?


  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true
  pod 'FirebaseAppCheckInterop', :modular_headers => true
  pod 'FirebaseAuthInterop', :modular_headers => true
  pod 'FirebaseMessagingInterop', :modular_headers => true
  pod 'GTMSessionFetcher', :modular_headers => true
  pod 'FirebaseStorageInternal', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true

Flipper is not going to work with use_frameworks - that's not fixed yet as far as I know:

  use_flipper!()

Does my demo script (still on 0.69.0, sorry - but reasonably representative) work for you? https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

Does it still work if you chop the installed modules down to just the ones you use?

octiva · 2022-07-20T01:50:34Z

Hey, im also experience the same issue, and have a very similar Podfile. This issue only seems to occur after adding firebase storage.

@mikehardy the usage of the specific pod 'Firebase', :modular_headers => true... come from this issue comment

We are using these in leu of the use_framework due to its incompatibility with Flipper.

I believe the issue may also be related to a recent issue in FirebaseUI-IOS here, which looks to have been resolved here.
Would be interested to know if the react-native-firebase package has incorporated these changes.

Keen to discuss, and if I find a working solution with Flipper, I will provide.

dpyeates · 2022-07-20T08:14:06Z

I'm getting this as well with FB Storage

I can confirm that if I remove @react-native-firebase/storage from my build then things work OK.

mikehardy · 2022-07-20T20:58:24Z

@octiva i just did a release last night that has latest iOS SDK dependency so if it's released, it's available here

Not sure what's going on with the storage compile fail? Dies the make-demo.sh I link everywhere work? It has storage and it works for me ? 🤔

octiva · 2022-07-20T23:25:49Z

@mikehardy I cant see the new release version, will this be v15.1.2?
EDIT: Release is v15.2.0

mikehardy · 2022-07-21T00:07:32Z

@mikehardy I cant see the new release version, will this be v15.1.2?

Apologies thought I published but did not, job running now...

octiva · 2022-07-21T04:29:07Z

@mikehardy I just tested v15.2.0 and unfortunately im still getting the same build error.

I have investigated a little more, but with no success. Will be moving on from this and following a less ideal path of using the Firebase web package in the app for Storage.

Will likely look to pick this back up at some point, but my gut feeling is that it is upstream of this package and likely needs to be resolved in FirebaseUI-iOS.

mikehardy · 2022-07-21T14:00:52Z

I read through the changes in linked FirebaseUI area, and this is the style of change they did:

https://github.com/firebase/FirebaseUI-iOS/pull/1029/files#diff-96e8c12e050b3b6165fc44b0c8302fcae849e20049f7bc93ff24c1ded1d64303

#if __has_include(<FirebaseStorage/FirebaseStorage.h>)
  // Firebase 8.x
  #import <FirebaseStorage/FirebaseStorage.h>
#elif __has_include(<FirebaseStorage/FirebaseStorage-Swift.h>)
  // Firebase 9.0+
  #import <FirebaseStorage/FirebaseStorage-Swift.h>
#else
  @import FirebaseStorage;
#endif

We are all 9+ though, so we just changed the import. I think cocoapods might generate that with use_frameworks, as that seems to be the variable here, that this is happening and if I understand correctly, the projects are attempting to set $RNFirebaseAsStaticFramework to true and use_modular_headers but not set use_frameworks itself ?

dpyeates · 2022-07-22T15:36:22Z

@mikehardy "if I understand correctly, the projects are attempting to set $RNFirebaseAsStaticFramework to true and use_modular_headers but not set use_frameworks itself ?", yes that is exactly the case. I cannot use use_frameworks as I also use react-native-skia which does not work with frameworks. The other FB modules work OK, it is just storage that seems to have an issue.

mikehardy · 2022-07-22T15:50:59Z

I think based on a thread upstream that cocoapods generates the Swift bridging header file for storage, only in response to the use frameworks toggle. This may be the fundamental reason for the new requirement to use that toggle, perhaps Paul Bausterien knows that for sure - I'm mobile and cannot tag them properly unfortunately

Fortidude · 2022-07-23T12:44:59Z

In file included from /client/node_modules/@react-native-firebase/app/ios/RNFBApp/RNFBAppModule.m:18:
/client/ios/Pods/Headers/Private/Firebase/Firebase.h:54:13: fatal error: 'FirebaseFunctions/FirebaseFunctions-Swift.h' file not found
    #import <FirebaseFunctions/FirebaseFunctions-Swift.h>
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

RN 0.68, firebase 15.2.0, podfile:

  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true
  pod 'FirebaseAppCheckInterop', :modular_headers => true
  pod 'FirebaseAuthInterop', :modular_headers => true
  pod 'FirebaseMessagingInterop', :modular_headers => true
  pod 'GTMSessionFetcher', :modular_headers => true
  pod 'FirebaseStorageInternal', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true

Any ideas? 🤔

mikehardy · 2022-07-23T18:01:02Z

@Fortidude this looks like the equivalent problem from storage except for functions. The firebase-ios-sdk release notes are clear, use_frameworks is required. Are you using that flag in your podfile? @paulb777 may be able to elaborate on this specific integration need in cocoapods? I had enough time just now to properly tag him in 😅

paulb777 · 2022-07-23T19:19:32Z

While the modular_headers workarounds may work for the other Firebase pods, with Firebase 9, frameworks are required for FirebaseStorage and FirebaseFunctions.

ithustle · 2022-07-24T17:08:57Z

While the modular_headers workarounds may work for the other Firebase pods, with Firebase 9, frameworks are required for FirebaseStorage and FirebaseFunctions.

@paulb777 can you show how to user modular_headers?

@mikehardy

The firebase-ios-sdk release notes are clear, use_frameworks is required

use_frameworks is conflicting with use_flipper ... How can we get away of that?

mikehardy · 2022-07-24T19:19:56Z

@ithustle you cannot get away from it I think.

Flipper must be fixed to work in use_frameworks mode, or you must disable Flipper, or you must stay on react-native-firebase <= v14

There is no other way I'm aware of

I'm working on these things (Flipper + use_frameworks compatibility, and Hermes + use_frameworks compatibility which will hopefully be in react-native 0.70) but it will take some time, months I suspect.

So I'm going to close this as a sort of "blocked by upstream" resolution.

for Functions and Storage you must have use_frameworks set. For others, at least for now, you may import them directly with modular_headers set but it is not supported, it just happens to work for now.

The use_frameworks setting does cause problems with other modules, and with Flipper, and with Hermes, but those are problems with those modules, with Flipper and with Hermes, and should be pursued as problems there. I'm doing that with Flipper and Hermes but now with other modules, I'll need other people to pursue those.

codekojo · 2022-07-25T19:46:43Z

I'm getting this as well with FB Storage

I can confirm that if I remove @react-native-firebase/storage from my build then things work OK.

I am getting the same error.

elinahovakimyan · 2022-07-25T20:00:57Z

I ended up downgrading to firebase@14 all the firebase packages to be able to use storage with flipper.

codekojo · 2022-07-25T20:22:10Z

I ended up downgrading to firebase@14 all the firebase packages to be able to use storage with flipper.

Can you share you package.json?

elinahovakimyan · 2022-07-25T20:29:57Z

Here are the packages I use and the Podfile

juanctecdam · 2022-07-25T21:23:06Z

Little frustating... I need to use Appcheck and as soon as I upgrade to version 15, I can't get a thing to work..

juanctecdam · 2022-07-26T08:26:53Z

@ithustle Thing is that I need to add to my project AppCheck which depends on the latest version(15) of RN Firebase. I tried to make it as modules, but it always complains about FirebaseStorage-Swift. I tried with use_frameworks and that stopped complaining about this library but I have another library not compiling.
Frustrating cause I can't get to fix this and we need a solution.

guthriet1230 · 2022-07-29T20:28:56Z

Any progress here? I'm stuck with the same error specific to Firebase Storage only (@15.2)

mikehardy · 2022-07-30T20:12:47Z

@juanctecdam AppCheck has been available for more than a year, it is available in v14.

Firebase storage and Firebase functions require use_frameworks! in your Podfile, it's what generates those files. If you can't use use_frameworks, and you ned functions and/or storage, you can't use v15. There's no simpler way to put it unfortunately. Use v14 in that case and help in the underlying issues (with flipper or whatever the 3rd party module is that has a problem) in order to get use_frameworks! to work then this whole thing will move forward and get easier for everyone

gitcoder-23 · 2022-09-02T07:50:19Z

hi,
I am facing same issue fatal error: 'FirebaseStorage/FirebaseStorage-Swift.h' file not found #import <FirebaseStorage/FirebaseStorage-Swift.h> .. please help to fix this problem

mikehardy · 2022-09-02T12:29:31Z

@gitcoder-23 that's what you see if you do not enable use_frameworks! :linkage => :static in your Podfile. Storage and functions require use frameworks unconditionally, the workarounds others mention are only valid temporarily (until other modules require it unconditionally) and are not valid for storage and functions. My last comment above states the same.

gitcoder-23 · 2022-09-02T13:23:52Z

@mikehardy Hi, Thanks. But now fatal error: 'FlipperKit/FlipperClient.h' file not found.. please help

mikehardy · 2022-09-02T13:52:09Z

@gitcoder-23 you must read the instructions. Flipper is not compatible with use_frameworks. This may not be what you want to hear but is nevertheless reality, and is documented:

https://rnfirebase.io/#altering-cocoapods-to-use-frameworks (big note there)
https://github.com/invertase/react-native-firebase/blob/main/CHANGELOG.md#breaking-changes Huge breaking changes note there

kaliseo34 · 2022-10-12T20:53:19Z

@gitcoder-23 you must read the instructions. Flipper is not compatible with use_frameworks. This may not be what you want to hear but is nevertheless reality, and is documented:

https://rnfirebase.io/#altering-cocoapods-to-use-frameworks (big note there) https://github.com/invertase/react-native-firebase/blob/main/CHANGELOG.md#breaking-changes Huge breaking changes note there

Hi,

Disabling Hermes & Flipper causes app crash on build by my side.. I'll need another solution to manage files for the moment :s

Anybody found the solution ?

mikehardy · 2022-10-12T21:01:18Z

Disabling Hermes & Flipper causes app crash on build by my side

That's really unexpected, if you provided any sort of details (https://stackoverflow.com/help/how-to-ask) I/we might be able to help. I can tell you that it should work though, I just re-ran my build test rig yesterday and it was fine https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

You probably don't need to disable Hermes though, for what it's worth. Hermes appears to work well now. Flipper still definitely not working.

kaliseo34 · 2022-10-12T21:29:47Z

I made some changes regarding your script :

Replacing use_frameworks! by use_frameworks! :linkage => :static
Moving $RNFirebaseAsStaticFramework = true from top of file to next line of use_frameworks
Uncomment line :flipper_configuration => FlipperConfiguration.enabled, & remplace enabled with disabled

And it worked !

Thanks a lot for your help !

danias · 2022-11-23T13:53:13Z

I made some changes regarding your script :

Replacing use_frameworks! by use_frameworks! :linkage => :static
Moving $RNFirebaseAsStaticFramework = true from top of file to next line of use_frameworks
Uncomment line :flipper_configuration => FlipperConfiguration.enabled, & remplace enabled with disabled

And it worked !

Thanks a lot for your help !

Can you please post the whole of your pod file?

mikehardy · 2022-11-27T02:54:28Z

@danias you can run this script any time

I keep it up to date / in sync with current react-native as I work with react-native releases group to test new releases so it's always pretty fresh

It generates a Podfile that works https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

alexander0205 · 2022-12-08T22:41:37Z

Is working for me with the version 14.11.1 and $FirebaseSDKVersion = '8.15.0'

alexander0205 · 2022-12-08T22:42:05Z

Here are the packages I use and the Podfile

And adding $FirebaseSDKVersion = '8.15.0'

mikehardy · 2022-12-08T22:57:54Z

It is working for you because you have specifically downgraded to a version of react-native-firebase that includes a version of firebase-ios-sdk from before they converted that to Swift (and before they started requiring use_frameworks)

So sure, if you downgrade you can "workaround" this problem.

However, you will have bought yourself other problems. Check the release notes and see if any of the changes between firebase-ios-sdk 8.15.0 and 10.2.0 (soon to be 10.3.0 here) are for issues that will cause you problems https://firebase.google.com/support/release-notes/ios

yoannes · 2022-12-12T05:57:19Z

This worked for me, thanks

#6382 (comment)

abumubaarak · 2022-12-27T06:05:18Z

I had to remove Flipper and add use_frameworks! :linkage => :static

mikehardy · 2022-12-28T15:07:52Z

I had to remove Flipper and add use_frameworks! :linkage => :static

Yes, as we document here: https://rnfirebase.io/#altering-cocoapods-to-use-frameworks

rishiankush · 2023-01-09T07:40:17Z

Not at all working for me. I tried every solution. Please check my podfile and screenshot for error below:

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '12.4'
install! 'cocoapods', :deterministic_uuids => false
use_frameworks! :linkage => :static
target 'lovelocalPartner' do
  config = use_native_modules!
  # Flags change depending on the env values.
  flags = get_default_flags()
  $RNFirebaseAsStaticFramework = true
  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    # Upcoming versions of React Native may rely on get_default_flags(), but
    # we make it explicit here to aid in the React Native upgrade process.
    :hermes_enabled => true,
    :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    # :flipper_configuration => FlipperConfiguration.enabled,
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )
  target 'lovelocalPartnerTests' do
    inherit! :complete
    # Pods for testing
  end
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end
end

nppull · 2023-02-09T07:58:48Z

react-native 0.70.0
react-native-firebase 17.0

add

target 'Example' do
config = use_native_modules!
$RNFirebaseAsStaticFramework = true
use_frameworks! :linkage => :static

and comment flipper

:flipper_configuration => FlipperConfiguration.enabled,

that work for me.

devlprkhan · 2023-09-12T20:46:08Z

Yes 🥹 🙌, Finally I resolve the issue,

Resolve react_native_pods.rb with node to allow for hoisting

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

use_modular_headers!

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

use_frameworks! :linkage => :static
end

target 'BoloNow' do
config = use_native_modules!
$RNFirebaseAsStaticFramework = true
use_frameworks! :linkage => :static

Flags change depending on the env values.

flags = get_default_flags()

pod 'Firebase', :modular_headers => true
pod 'FirebaseCore', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
pod 'FirebaseStorage', :modular_headers => true
pod 'FirebaseAppCheckInterop', :modular_headers => true
pod 'FirebaseAuthInterop', :modular_headers => true
pod 'FirebaseCoreExtension', :modular_headers => true
pod 'GTMSessionFetcher', :modular_headers => true
pod 'FirebaseFunctions', :modular_headers => true
pod 'FirebaseMessagingInterop', :modular_headers => true
pod 'RNFBFirestore', :path => '../node_modules/@react-native-firebase/firestore'
pod 'RNFBStorage', :path => '../node_modules/@react-native-firebase/storage'

use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
:hermes_enabled => flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
:flipper_configuration => FlipperConfiguration.disabled,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)

target 'BoloNowTests' 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
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end

end

RKhatri93 · 2023-12-13T10:34:35Z

I've encountered persistent challenges integrating Firebase Cloud Functions and Storage in my React Native project. Despite previous attempts and following suggestions, the error related to 'FirebaseFunctions/FirebaseFunctions-Swift.h' file persists.

Key Points:
React Native Version: 0.72.6
Firebase Version: 18.7.3
With new react native architecture
Firebase Pods Configuration: Firebase pods were added with modular headers

What I've Tried:
Checked and reconfirmed pod configurations.
Reviewed and ensured Firebase pods were correctly linked.

Current Impact:
This issue continues to prevent the utilization of essential Firebase features crucial for the app's functionality.

Request:
Seeking further assistance or alternative solutions to resolve this persisting issue and successfully integrate Firebase Cloud Functions and Storage into the React Native project. Any new insights or suggestions are greatly appreciated. Thank you for your ongoing support.

mikehardy · 2023-12-13T17:42:05Z

Firebase Pods Configuration: Firebase pods were added with modular headers

Don't do that, or if you do that do not come here for support.

use_frameworks! :linkage => :static is a STRICT REQUIREMENT as documented

You are attempting to use the module contrary to the documentation so no support is provided

russplusplus · 2023-12-19T04:24:17Z

Hey all, I had the same problem and following the "Getting Started" instructions on this page completely solved it for me: https://rnfirebase.io/

n-kulic · 2024-01-08T19:08:48Z

@ithustle you cannot get away from it I think.

Flipper must be fixed to work in use_frameworks mode, or you must disable Flipper, or you must stay on react-native-firebase <= v14

There is no other way I'm aware of

I'm working on these things (Flipper + use_frameworks compatibility, and Hermes + use_frameworks compatibility which will hopefully be in react-native 0.70) but it will take some time, months I suspect.

So I'm going to close this as a sort of "blocked by upstream" resolution.

for Functions and Storage you must have use_frameworks set. For others, at least for now, you may import them directly with modular_headers set but it is not supported, it just happens to work for now.

The use_frameworks setting does cause problems with other modules, and with Flipper, and with Hermes, but those are problems with those modules, with Flipper and with Hermes, and should be pursued as problems there. I'm doing that with Flipper and Hermes but now with other modules, I'll need other people to pursue those.

Hello, checking back on this.
Has there been progress or changes in debugging React Native in this context (use_frameworks conflicting with use_flipper)? Any other workarounds besides downgrading firebase packages?
Any insights would be appreciated!

mikehardy · 2024-01-30T16:15:56Z

No. firebase-ios-sdk requires use_frameworks, and Flipper does not work with it.
Moreover, Flipper is deprecated in the react-native ecosystem, so this will likely never change.

Before anyone posts on this again and triggers notifications please do the research - answer these questions 1) is Flipper still the way to debug things in react-native and 2) after checking the Flipper repo does it work with use_frameworks?

Check those things. Answer yes to both questions if you can, then post.

tunadag · 2024-08-17T14:15:33Z

Hey all, I had the same problem and following the "Getting Started" instructions on this page completely solved it for me: https://rnfirebase.io/

Thanks a lot, actually you made my day, I was struggling with it for hours, that documentation also solved it for me.

nicolas-wl added help: needs-triage Issue needs additional investigation/triaging. type: bug New bug report labels Jul 11, 2022

mrkpatchaa mentioned this issue Jul 14, 2022

[🐛] The following Swift pods cannot yet be integrated as static libraries [has workaround / Need Expo instructions to close this] #6332

Closed

10 tasks

dpyeates mentioned this issue Jul 20, 2022

SkData.h not found when using use_frameworks! Shopify/react-native-skia#652

Closed

mikehardy closed this as completed Jul 24, 2022

mikehardy added platform: ios blocked: react-native Issue or PR blocked by a React Native issue or change. Resolution: Solution Provided and removed type: bug New bug report help: needs-triage Issue needs additional investigation/triaging. labels Jul 24, 2022

paulb777 mentioned this issue Aug 25, 2022

fatal error: 'FirebaseStorage/FirebaseStorage-Swift.h' file not found #import <FirebaseStorage/FirebaseStorage-Swift.h> firebase/firebase-ios-sdk#10135

Closed

kickbk mentioned this issue Feb 23, 2023

[REQUEST] Support use_frameworks! star-micronics/react-native-star-io10#90

Closed

paulb777 mentioned this issue Mar 30, 2023

fatal error: No type or protocol named 'FIRLibrary' FirebaseStorage-Swift.h firebase/firebase-ios-sdk#11045

Closed

[🐛] 'FirebaseFunctions/FirebaseFunctions-Swift.h' file not found #6382

[🐛] 'FirebaseFunctions/FirebaseFunctions-Swift.h' file not found #6382

Comments

nicolas-wl commented Jul 11, 2022 • edited Loading

mikehardy commented Jul 15, 2022

octiva commented Jul 20, 2022 • edited Loading

dpyeates commented Jul 20, 2022 • edited Loading

mikehardy commented Jul 20, 2022 • edited Loading

octiva commented Jul 20, 2022 • edited Loading

mikehardy commented Jul 21, 2022

octiva commented Jul 21, 2022

mikehardy commented Jul 21, 2022

dpyeates commented Jul 22, 2022 • edited Loading

mikehardy commented Jul 22, 2022 • edited Loading

Fortidude commented Jul 23, 2022

mikehardy commented Jul 23, 2022

paulb777 commented Jul 23, 2022

ithustle commented Jul 24, 2022 • edited Loading

mikehardy commented Jul 24, 2022

codekojo commented Jul 25, 2022 • edited Loading

elinahovakimyan commented Jul 25, 2022

codekojo commented Jul 25, 2022

elinahovakimyan commented Jul 25, 2022

juanctecdam commented Jul 25, 2022

juanctecdam commented Jul 26, 2022

guthriet1230 commented Jul 29, 2022

mikehardy commented Jul 30, 2022

gitcoder-23 commented Sep 2, 2022

mikehardy commented Sep 2, 2022

gitcoder-23 commented Sep 2, 2022

mikehardy commented Sep 2, 2022

kaliseo34 commented Oct 12, 2022

mikehardy commented Oct 12, 2022 • edited Loading

kaliseo34 commented Oct 12, 2022

danias commented Nov 23, 2022

mikehardy commented Nov 27, 2022

alexander0205 commented Dec 8, 2022

alexander0205 commented Dec 8, 2022

mikehardy commented Dec 8, 2022

yoannes commented Dec 12, 2022

abumubaarak commented Dec 27, 2022

mikehardy commented Dec 28, 2022

rishiankush commented Jan 9, 2023

nppull commented Feb 9, 2023

devlprkhan commented Sep 12, 2023

Resolve react_native_pods.rb with node to allow for hoisting

use_modular_headers!

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 } } } : {}),

```

use_frameworks! :linkage => linkage.to_sym

Flags change depending on the env values.

RKhatri93 commented Dec 13, 2023

mikehardy commented Dec 13, 2023

russplusplus commented Dec 19, 2023 • edited Loading

n-kulic commented Jan 8, 2024

mikehardy commented Jan 30, 2024

tunadag commented Aug 17, 2024

nicolas-wl commented Jul 11, 2022 •

edited

Loading

octiva commented Jul 20, 2022 •

edited

Loading

dpyeates commented Jul 20, 2022 •

edited

Loading

mikehardy commented Jul 20, 2022 •

edited

Loading

octiva commented Jul 20, 2022 •

edited

Loading

dpyeates commented Jul 22, 2022 •

edited

Loading

mikehardy commented Jul 22, 2022 •

edited

Loading

ithustle commented Jul 24, 2022 •

edited

Loading

codekojo commented Jul 25, 2022 •

edited

Loading

mikehardy commented Oct 12, 2022 •

edited

Loading

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`

russplusplus commented Dec 19, 2023 •

edited

Loading