Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🐛] Expo - ios React Native Firebase - pod install not working #6323

Closed
rahul2992 opened this issue Jun 21, 2022 · 11 comments
Closed

[🐛] Expo - ios React Native Firebase - pod install not working #6323

rahul2992 opened this issue Jun 21, 2022 · 11 comments
Labels
resolution: needs-repro This issue could be reproduced or needs a repro provided.

Comments

@rahul2992
Copy link

rahul2992 commented Jun 21, 2022

Hi everyone

I am trying to use expo with react native firebase in the config plugin as explained on the link

The installation is working for android, but for ios I am running in the following error. Any guidance would be helpful. Thank you

⚠️ Something went wrong running pod install in the ios directory.
Command pod install failed.
└─ Cause: The following Swift pods cannot yet be integrated as static libraries:

The Swift pod FirebaseCoreInternal depends upon GoogleUtilities, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.

I have tried running with use_modular_headers! in the PodFile to install the pods. Post which I run into the following issue:

510 |
511 | // They need the definitions of integer types.

512 | #include "glog/log_severity.h"
| ^ import of module 'glog.glog.log_severity' appears within namespace 'google'
513 | #include "glog/vlog_is_on.h"
514 |
515 | // Initialize google's logging library. You will see the program name

@rahul2992 rahul2992 added help: needs-triage Issue needs additional investigation/triaging. type: bug New bug report labels Jun 21, 2022
@mikehardy
Copy link
Collaborator

Hi there! You've ignored our issue template and not specified steps to reproduce
https://stackoverflow.com/help/how-to-ask
https://stackoverflow.com/help/minimal-reproducible-example

Perhaps if you included every single command line you run / config file contents required to start from scratch constructing an example others could follow along and reproduce the issue?

Please note that not everyone uses Expo, in particular none of the primary maintainers here do, so as you ask for help in non-expo modules you need to be quite specific and include reproduction information like this

@mikehardy mikehardy added resolution: needs-repro This issue could be reproduced or needs a repro provided. Resolution: No Template and removed type: bug New bug report help: needs-triage Issue needs additional investigation/triaging. labels Jun 21, 2022
@rocket13011
Copy link

Hello, I have exactly the same error in react-native 0.68.2

I simply updated the version from ^14.0.0 to

"@react-native-firebase/app": "^15.0.0",
"@react-native-firebase/messaging": "^15.0.0"

once done I did an npm update then an arch -x86_64 pod update which gives the same error from above.

Sincerely.

@mikehardy
Copy link
Collaborator

@rocket13011 that's insufficient as a problem description

My comment was quite specific and prescriptive, please read it entirely and include requested information

@rocket13011
Copy link

I solved my problem by putting :
pod 'GoogleUtilities', :modular_headers => true in podfile so that it updates before FirebaseCoreInternal otherwise there is an error.

@mikehardy
Copy link
Collaborator

With apologies, please let me set clear expectations

  • none of the primary maintainers use Expo
  • You must be very specific about exactly how to reproduce your problems starting from scratch.
  • In general you should expect that Expo-specific problems must be solved by Expo community members.
  • If there are deficiencies in the Expo-specific instructions and/or the Expo config plugins they will necessarily require Expo-community members to post PRs to repair them.

We provide a module that is tested thoroughly in a non-Expo environment.
I provide a reproduction script that builds it and runs it from scratch in a non-Expo environment https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

That's our commitment currently as maintainers. We need the Expo community to step up directly for Expo-specific issues, and our commitment is to then merge things for Expo folks, but we will likely not be able to actually help you troubleshoot much or create PRs.

@rahul2992
Copy link
Author

@mikehardy - Thank you. Noted.
@rocket13011 - Will try the fix you cited.

@RodolfoGS
Copy link

I created a new issue with the steps to reproduce and a repo: #6332

@mikehardy

This comment was marked as duplicate.

@mikehardy
Copy link
Collaborator

I just realized I'm on a closed issue and your repro is on the new issue, I am going to re-post there and hide my comment here to keep conversation in one spot where possible

@Aris-ngoy
Copy link

I solved my problem by putting :
pod 'GoogleUtilities', :modular_headers => true in podfile so that it updates before FirebaseCoreInternal otherwise there is an error.

thanks

@TowhidKashem
Copy link

I solved my problem by putting :

pod 'GoogleUtilities', :modular_headers => true in podfile so that it updates before FirebaseCoreInternal otherwise there is an error.

Hey there! I take it you're on the unmanaged workflow? I'm on managed so don't have the iOS folder and associated pod files exposed.

I think the solution needs to be on the config plug-in level for it to work on the managed workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: needs-repro This issue could be reproduced or needs a repro provided.
Projects
None yet
Development

No branches or pull requests

6 participants