-
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
pod install fails (not M1) — 401 when installing Boost #33462
Comments
I found a workaround, though admittedly it's pretty lame and is no better than a bandaid solution. The approach is to download the file and then source it from the local filesystem, rather than making a network call:
note: you may need to adjust the version of the boost package your project specifies. |
try |
@Tycholiz Have you got the solution? Actually, I got the same error but I am using Mac with M1 chip. |
No solution yet unfortunately. With my workaround above I haven't ran into the issue since. I expect it will poke its head soon though. |
bump on this issue Tried to initialize a new project today and got the 401 again, this time on OpenSSL package. |
@Tycholiz I resolved my issue with command: |
No luck, still getting error:
I also get the following error when running the initial
Although as noted, it's not a critical error. Nonetheless I don't understand why any of these issues would be happening for only some people but not all. |
@Tycholiz I resolved this issue by removing the following line from ~/.netrc.
|
Updating cocoapods via |
Closing as I believe this was a transient issue, related to local network configuration (.netrc file, VPNs or flakyness on cocoapod side). Feel free to re-open if the issue persists consistently. I've also tested this locally on the RC for 0.69, and everything works 👍 |
I experienced this yesterday - no idea why. The boost install step has been hanging for several years for me. Only happens occasionally. I thought maybe it was a DNS issue or something like that, tried using a VPN (I'm in the EU). Anyway, this clean step worked for me:
...then run The key fix for me was adding |
I am having the same error. @Tycholiz did you fix it? |
I did not. The workaround I posted above was sufficient to move past |
@Tycholiz the only workaround that I see you posted is about the 401 aover boost_1_76_0.tar.bz2, but in this case the problem is about "Error installing OpenSSL-Universal", are them related? |
Replaced spec.source = { :http => 'https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76_0.tar.bz2',
spec.source = { :http => 'https://sourceforge.net/projects/boost/files/boost/1.76.0/boost_1_76_0.tar.bz2'} |
@URvesh109 Thanks but it didn't work |
I'm pretty sure this issue is related to something at the network level. I'm not sure what my exact setup was at the time, but see if you are on a VPN. Maybe even try a different wifi network to see if the result changes. It's quite a strange issue and I'm not exactly sure what to think about it |
@Tycholiz true it is strange issue |
Thanks |
It works for me |
I am still seing this issue. Is there anything besides the workaround? A lot of people seem to have reported this. |
Worked for me:
|
What worked for me was just waiting the download... The link was downloading on an average of 25KB/s. |
This worked for me. Thank you |
For workaround solution. You don't need to download the tar.bz2. And move to node_modules/react-native/third-party-podspecs. i think jfrog close their server. You may need to change 76 if you use another version |
this worked for me |
Connecting to another wifi(iPhone hotspot) solved the issue for me. |
hit the same command |
I tried to run the curl command itself ( Btw I have this problem while installing mapbox. |
This is really worked for me. Thanks a lot :) |
oh thank you, It's work for me. |
running is this okay? either way, this solution sadly didnt work for me. manually editing is this a widespread problem people have? i just got the problem yesterday, while this issue is a year old. |
did you find out any work around @Adnan-Bacic ? |
@aleena-adnan1 as someone else suggested, i just waited. it takes a very long time. i honestly didnt look at the time but i guess it was at least 30 min, if not 60+ |
@Adnan-Bacic Despite waiting, did it work or no? |
Yes it worked |
It works for me!!!! |
Updating cocoapods via sudo gem install cocoapods fixed this issue. |
/usr/bin/tar xf /var/folders/_y/1jlgk27j6xz72bwmny4f2_cw0000gq/T/d20230915-6496-r9jxag/file.tbz -C /var/folders/_y/1jlgk27j6xz72bwmny4f2_cw0000gq/T/d20230915-6496-r9jxag tar: Error opening archive: Unrecognized archive format |
@cairocampos we updated sudo command and manual steps also we are getting the below error /usr/bin/tar xf /var/folders/_y/1jlgk27j6xz72bwmny4f2_cw0000gq/T/d20230915-6496-r9jxag/file.tbz -C /var/folders/_y/1jlgk27j6xz72bwmny4f2_cw0000gq/T/d20230915-6496-r9jxag tar: Error opening archive: Unrecognized archive format when we navigate the below path we unable to identify the file file.tbz But we got unrecognized archive format. I'm wonder how to identify the root cause. |
|
Maybe it would be ridiculous but switching from WiFi to LTE makes it load in 2 minutes, WiFi it showed me like >2 hours btw my wifi is faster than LTE) |
The build process stopped with errors the first time when I ran the command --platform ios --lcal once. But after running the command for the second time, boost installing took about 20 minutes and finally the build was successfully made. |
This Worked for me as well. |
this solution saved my project 🥹 |
After One year, react teams are not offically fix this issue . |
not really see pin issue from maintainer |
Description
Following the docs, I'm initializing a new react-native with Typescript repo with the command
Upon running that command, I get the following:
So I
cd
into theios/
directory and runpod install
. Everything installs propery, but when I get to boost...I understand that it's the request to
jfrog.io
that's giving me the 401, but how do I get around this? I'm not even clear on why access to this package would be forbidden in the first place. Strangely, I can install the tar.bz2 file directly just by putting that URL into my address bar. Why would it return a 401 to cURL?I'm a web developer so I'm used to the npm ecosystem and have never faced a 401 before.
What can I do to move past this?
Version
0.67.4
Output of
npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 12.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 294.95 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.19.1 - /usr/local/opt/node@14/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 6.14.16 - /usr/local/opt/node@14/bin/npm
Watchman: 2021.10.18.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 28, 29
Build Tools: 28.0.3, 29.0.3
System Images: android-26 | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6392135
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_252 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.4 => 0.67.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
ios
pod install
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: