-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
iOS Command PhaseScriptExecution failed - Assumptions about 'head' utility on the execution PATH #5801
Comments
Interesting - is there any output in the build log showing what the error was? That is our Xcode script but we need to see the actual error if possible. |
|
What do you mean by re-arranging my path? Are you saying it could be because I'm using a web based utility which is the result of this error? So I might have to install react-native cli do I? |
The binary first on your path named head is not the one we expect. We expect a standard bsd utils binary and instead it's some web thing Open terminal to test it. Type 'which head' or 'whereis head' to see what's what. You can search web for this as well and it'll probably give some insight |
https://ss64.com/osx/head.html vs some utility you have installed that's doing the equivalent of this https://stackoverflow.com/questions/217955/how-to-do-a-http-head-request-from-the-windows-command-line |
I ran I think it could be because I set my default php path to go to XAMPP so I more or less think I have to change back to the default path on my computer. I'll see about that |
It appears we have an expectation about what `head` binary will do, and XAMMP at least bundles a different `head` which does not meet our expectations. This is a basic unix utility on all macs via the base install, so the full path to the base install version should be a reasonable fix Fixes #5801
I made a PR to use the fully-specified path |
It appears we have an expectation about what `head` binary will do, and XAMMP at least bundles a different `head` which does not meet our expectations. This is a basic unix utility on all macs via the base install, so the full path to the base install version should be a reasonable fix Fixes #5801
Well, your hunch was right. Indeed it was a problem with the head or whatever you said it was. Apparently I decided to change my default php path to point to the one in xampp not knowing that it would have certain repercussions. Thanks |
I just published 12.9.3 https://github.com/invertase/react-native-firebase/blob/master/CHANGELOG.md#1293-2021-10-22 which should allow you to use XAMMP in the way you like without this build issue here I see you've edited out the question about overriding iphone deployment versions. I'm only commenting on it to say: Oh, man! That was an odyssey to fix. But it is fixed in react-native 0.66.1 with at least a workaround that's easy to adopt, and in 0.67.0 (currently in -rc.0 status, but works) it's fixed for real. iOS compiles were a serious mess in react-native 0.64, 0.65 etc and it drove me crazy so yes, I did something about it ;-). Cheers |
Issue
I am aware that this issue has been brought up before and I am very sure that I followed the documentation properly and I have also looked up on those issues that are related to my question.
So I installed the packages
@react-native-firebase/app
and@react-native-firebase/messaging
because all I want to use Firebase is for Cloud Messaging. I followed the setup as indicated in the documentation and ran the usualpod install
in the ios folder of my project. I also added an emptyfirebase.json
file that was instructed here.However, after doing all that, my build still fails. With the output saying:
When I open the script that was stated in the output, it shows this:
Project Files
Javascript
Click To Expand
package.json
:firebase.json
for react-native-firebase v6:{ "react-native": { } }
iOS
Click To Expand
ios/Podfile
:Android
Click To Expand
Have you converted to AndroidX?
android/gradle.settings
jetifier=true
for Android compatibility?jetifier
for react-native compatibility?android/build.gradle
:// N/A
android/app/build.gradle
:// N/A
android/settings.gradle
:// N/A
MainApplication.java
:// N/A
AndroidManifest.xml
:<!-- N/A -->
Environment
Click To Expand
react-native info
output:react-native-firebase
version you're using that has this issue:e.g. 5.4.3
Firebase
module(s) you're using that has the issue:e.g. Instance ID
TypeScript
?No
React Native Firebase
andInvertase
on Twitter for updates on the library.The text was updated successfully, but these errors were encountered: