Running pod install fails with JSON::ParseError #12115
Comments
|
I found an identical issue 9814 where updating to a newer version of Cocoapods and clearing caches was the recommended solution. However neither (am on the latest Homebrew version and have cleared caches multiple times) seem to resolve this issue. In the linked issue I see it mentioned that this may be due to the CDN delivering the file as empty. Since this happens persistently to the same file when the |
|
This one seems to be related: braintree/braintree_ios#1120 |
|
I am not able to reproduce with this FirebaseCoreExtenstion dependency though, it is not empty for me ( |
|
Looks like I have other empty podspec files as well: |
|
Not sure if this is related or not, but one thing I observed is that the ones that are empty locally return a For example: https://cdn.cocoapods.org/Specs/d/a/5/Braintree/6.8.0/Braintree.podspec.json -> redirects to https://cdn.jsdelivr.net/cocoa/Specs/d/a/5/Braintree/6.8.0/Braintree.podspec.json which returns status 200 and the https://cdn.cocoapods.org/Specs/d/a/5/Braintree/6.7.0/Braintree.podspec.json -> redirects to https://cdn.jsdelivr.net/cocoa/Specs/d/a/5/Braintree/6.7.0/Braintree.podspec.json which returns status 200 without the |
|
I am having the same issue but in my case Specs/5/9/a/Google-Mobile-Ads-SDK/10.9.0/Google-Mobile-Ads-SDK.podspec.json is empty but has content if I access it in the browser. |
|
@dchis If you open https://cdn.cocoapods.org/Specs/5/9/a/Google-Mobile-Ads-SDK/10.9.0/Google-Mobile-Ads-SDK.podspec.json in browser, which link it is redirecting to, and do you see the |
|
this helped me. I'm currently in easter europe and i cannot successfully download from the cdn. Changed to using USA east coast vpn and my issue was solved. https://stackoverflow.com/a/77368123/10458873 hope this helps! |
|
Hello @mlazari @dchis the root cause of the problem is in content-encoding header in response which is not supported by libcurl #12110 (comment). |
|
@sergeimikhan Thank you, I think you're right. I didn't see that difference in the browser, it was returning For me it started happening on the |
|
A colleague and I also get this error when trying to run pod install. Everyone at my work is able to run it, however, we are the only ones with the latest version of cocoapods and ruby from brew install cocoapods. If anyone has a solution that would be great. Here is the error I am getting, however I have tried several things and have gotten several errors related to trying to run 'pod isntall' [!] Invalid |
|
@SethY8s That looks like a different issue to me. |
|
Same here, it started happening on the Braintree pod recently |
|
so the current recommended workaround is using a VPN with a US address? this bug renders the entire build pipeline unusable. |
|
Changing VPN to US worked. This is crazy and sad. |
|
Can confirm using a VPN and selecting the USA worked. That being said, I also had to delete my node_modules and the lock file before reinstalling them and running "pod install" |
|
Confirm that using VPN with USA ip fixes the issue. |
|
The original issue reported in this ticket has now been solved (in all likelihood the changes made to Cocoapods CDN configuration, as discussed in #12110), and so I am closing the issue. |
|
@HrafnPrescriby It's still not fixed for me, but since this is a duplicate issue I think it's ok to close. |
You saved me hours bro, thanks. |
|
I tried using vpn also but it won't work in my case |
Command
Report
What did you do?
Ran a
pod installinside the iOS part of a Flutter project. Before running the command above I had already cleared the cache as per @dnkoutso's suggestions found in issue 9672.What did you expect to happen?
Installation should have worked.
What happened instead?
Based on the error message there is a flaw in the JSON file expected to be at
'/Users/hrafn/.cocoapods/repos/trunk/Specs/4/7/f/FirebaseCoreExtension/10.0.0/FirebaseCoreExtension.podspec.json'..It would seem that the file is generated but is empty:
Whereas the same file for other options is not:
Running
pod install --verbosegave me the following in case it is of any use (it does surface the link to the remote JSON file that turns out to be empty locally but is not remotely: link)Stack
Plugins
Podfile
Error
The text was updated successfully, but these errors were encountered: