Description
Environment
react-native-cli: 2.0.1
react-native: 0.55.3
OS: macOS High Sierra 10.13.4
Node: 8.11.1
Yarn: Not Found
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.3 Build version 9E145
Android Studio: Not Found
Steps to Reproduce
This is a whole new project using react-native init.
1: Using the react-native run-ios startup project will stay on the way (with screenshots below), and no further execution.
2: Open the project in Xcode, and start the emulator to stay in the "Building demo: double-conversion | Running 1 of 1 custom shell scripts", and the cut is no longer executed without any error.
Expected Behavior
The program is executed normally and the simulator can be started.
Actual Behavior
I'm not sure that my question is the same as #15469 , and the solution I gave in #15469 doesn't seem to solve my problem.
Activity
react-native-bot commentedon Apr 23, 2018
Thanks for posting this! It looks like your issue may be missing some necessary information. Can you run
react-native info
and edit your issue to include these results under the Environment section?Thank you for your contributions.
geekwill commentedon Apr 23, 2018
@react-native-bot Thanks for your reply. I have executed the
react-native info
according to your requirements, and I have edited the Environment information of issue.timwangdev commentedon Apr 23, 2018
Here is the custom shell script that blocks you:
https://github.com/facebook/react-native/blob/master/scripts/ios-install-third-party.sh
Try to set up a proxy for github and s3 urls.
geekwill commentedon Apr 23, 2018
@timwangdev Thank you for your reply. I did find out that it was caused by the network. What puzzles me is that my development environment is proxies. Fortunately I saw @pampang answer in #14423 and solved my problem.
I manually downloaded the four
.tar.gz
files required fornode_modules/react-native/ios-install-third-party.sh
to local, copied to~/.rncache/
and re-executedreact-native run-ios
command to achieve my desired effect, the program starts normally.timwangdev commentedon Apr 23, 2018
@geekwill No problem.