-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Pod install fails after ejecting to ExpoKit #436
Comments
Hi! Can you try this again? That error looks like cocoapods failed to download the tarball. |
I tried it on a different laptop with a different account and the same error appears.
|
that's pretty strange -- boost is a popular package and we don't do anything different with it. perhaps there is a network problem? also hi @nickjanssen 👋 |
I am experiencing this issue. There is no network problem. @brentvatne |
Hi! I'm still not able to reproduce this issue, do you have any more information that would help us identify the cause here? |
Not sure if it's kosher but running |
@dikaiosune I'll see if I can create a dockerfile to reproduce this. @brentvatne Hey! ;) |
I had this same error, the spec download url points to a sourceforge page with a redirect, and that redirect is where it fails. [!] Error installing boost
Quick FixFind this file on your system and edit it's source url. Find the boost spec file locallyopen ~/.cocoapods/repos/master/Specs/9/9/d/boost/1.59.0/boost.podspec.json Change the source download url to a direct link "source": {
"http": "https://downloads.sourceforge.net/project/boost/boost/1.59.0/boost_1_59_0.tar.gz?r=&ts=1513105136&use_mirror=kent"
}, Pod install with patience# everything should work - boost can be downloaded and unpacks
# Note this takes a while to compile, be patient.
pod install |
To build upon @lakhman's answer, what solved this for me was to go to the SourceForge page here and get the link it provides for you when you click the Be prepared, it takes forever. |
Somehow not even adding a direct link into podspec solved my problem, in my case what solved was to download the boost_1_59_0.tar.gz from sourceforge and serve it locally with a local http server, so afterwards I could edit the boost.podspec file pointing it to http://localhost:8080/boost_1_59_0.tar.gz |
Hi everyone! Looks like these issues should be cleared up by changes in facebook/react-native#16756. Once that lands it'll make it out in a future release. If that doesn't fix these issues, please feel free to ping me here and I'll reopen or open a new issue. Thanks! |
@anp still experiencing this |
@corysimmons CRNA doesn't support 0.54 yet because Expo had to delay our release: https://blog.expo.io/sdk-26-delayed-until-end-of-march-d02243e6ae7e |
|
Expected Behavior
It seems CRNA's eject is broken:
Observed Behavior
Environment
npm ls react-native-scripts
: (N/A since I ejected)npm ls react-native
: 0.48.3npm ls expo
: 21.0.2node -v
: 6.9.5npm -v
: 4.6.1yarn --version
: 0.27.5watchman version
: 4.6.0pod --version
: 1.3.1The text was updated successfully, but these errors were encountered: