-
Notifications
You must be signed in to change notification settings - Fork 24k
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
Flipper-Glog (0.3.6) build fails if Xcode application name contains a blank space #29203
Comments
Encountered a same error message, but Xcode application name doesn't contain a black space. xcode-select --print-path checking whether make supports nested variables... yes |
That's really weird, but just renaming the Xcode, removing the blank space worked for me as well. |
It's actually not that weird. If the application name is not properly quoted in the script, the blank space will break the syntax and the script will fail. |
@madeinquant Thanks that was it! |
Woah! This was the issue. I had XCode inside of my SSD which had a whitespace in the name and that was causing the issue. Thanks a lot man |
i ju
Work for me |
After all attempts and no luck, try restarting the mac |
In my case. Docker was using the 8081 port so the xcode was not able to work. When I stoped the docker container |
In my case I have just disable the Roseta in to the Ternimal then run I am on M1 pro v |
is solve my issues:#32291 |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Description
The build of Flipper-Glog (0.3.6) using 'pod install' fails if the Xcode application name contains a blank space.
React Native version:
Steps To Reproduce
sudo xcode-select --switch /Applications/Xcode-beta\ 12.0.app
pod install
Expected Results
I would expect Flipper-Glog (0.3.6) to build properly, whatever the Xcode application name is.
Instead, it fails as follows:
This seems due to the configure script not being able to handle spaces in the application name (and it's probably true for other unusual characters too).
The text was updated successfully, but these errors were encountered: