Cocoapods: 🆘 [!] CDN: trunk Repo update failed

[vandadnp]

Hi

I am using Cocoapods 1.10.1 and when I do the following:

bundle exec pod install

I get the following error:

bundle exec pod install Analyzing dependencies [!] CDN: trunk Repo update failed - 2 error(s): CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/8/e/9/RxCoreData/0.3.0/RxCoreData.podspec.json Response: 429 429: Too Many Requests CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/8/e/9/RxCoreData/1.0.0/RxCoreData.podspec.json Response: 429 429: Too Many Requests

I try to open the failing URL in my browser and I see this:

This issue started happening this morning, just an hour ago. I have never had this issue before

I have also tried using the following in my Podfile

source 'https://github.com/CocoaPods/Specs.git'

But I keep getting CDN errors

I've switched to Wifi and then back to Ethernet and nothing helps. I even tried sharing network from my phone to my computer to see if it's my network causing the problem but it isn't.

[peppesapienza]

Hi guys,

I'm having the same issue locally (after uninstalling cocoapods) and on Azure DevOps Pipeline

I also tried to add source 'https://cdn.cocoapods.org/' to my Podfile, but I'm getting the same error

Thanks

[budioktaviyan]

Same here, got similar issue on serveral pods, like this one

https://cdn.jsdelivr.net/cocoa/Specs/5/b/f/ImageViewer/1.0/ImageViewer.podspec.json

[vandadnp]

Same here, got similar issue on serveral pods, like this one

https://cdn.jsdelivr.net/cocoa/Specs/5/b/f/ImageViewer/1.0/ImageViewer.podspec.json

I can open that particular URL and strange enough I can now open the original URL that I couldn't open previously

But it's failing on this one for me now

https://cdn.jsdelivr.net/cocoa/Specs/a/4/f/Giphy/1.2.5/Giphy.podspec.json

They seem to have some CDN issues

[vandadnp]

Some of the CDN problems have been fixed as of the time of this writing unfortunately replaced by other problems:

```bundle exec pod update --repo-update
Update all pods
Updating local specs repositories
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "Firebase/Crashlytics":
In Podfile:
Firebase/Crashlytics (= 7.8.0)

None of your spec sources contain a spec satisfying the dependency: Firebase/Crashlytics (= 7.8.0).

You have either:

• mistyped the name or version.
• not added the source repo that hosts the Podspec to your Podfile.
  ```

Crashlytics 7.8.0 is the latest release of Crashlytics and should exist

[sainianil]

I'm also facing similar issues for the last two days. Sometime it'll work properly however sometime it won't. Today since morning it is not working. Just got 2 successful builds and the issue started re-appearing again.

[awaisiosdev]

We are also having a similar problem. It started happening for us in this morning. We are using cocoa pods 1.10.0

[vandadnp]

[bangfika]

I faced the same issue. It was ok yesterday!

[sohail-dragon]

We're facing the same issue. Any workaround?

[DanielIzhevsk]

Have got the same issue this morning.

[Albert221]

Same error persisting on Bitrise CI/CD

[ds300]

We're seeing similar errors at Artsy on CircleCI

[DanielIzhevsk]

Temporary workaround:

1. Add this to top of your Podfile:
   source 'https://github.com/CocoaPods/Specs.git'
2. Remove Podfile.lock and Pods folder
3. Run pod install --repo-update

After that, you can push this changes to your repository.

[vandadnp]

Temporary workaround:

1. Add this to top of your Podfile:
   source 'https://github.com/CocoaPods/Specs.git'
2. Remove Podfile.lock and Pods folder
3. Run pod install --repo-update

After that, you can push this changes to your repository.

That doesn’t work for us. The old non CDN spec repo doesn’t include the latest pod specs and fails in building for us

[StefanBouwer]

Temporary workaround:

1. Add this to top of your Podfile:
   source 'https://github.com/CocoaPods/Specs.git'
2. Remove Podfile.lock and Pods folder
3. Run pod install --repo-update

After that, you can push this changes to your repository.

This also did not work for us. We are experiencing the same issue with dependencies like AFNetworking, Firebase, OCMock, etc.

[gklka]

Temporary workaround:

1. Add this to top of your Podfile:
   source 'https://github.com/CocoaPods/Specs.git'
2. Remove Podfile.lock and Pods folder
3. Run pod install --repo-update

After that, you can push this changes to your repository.

Worked for 3 of my projects.

[slajar]

I have the same issue in Azure devops. Sometimes it works sometimes it fails :/
I assume the CDN is way too picky regarding IP blocks and their requests, since a lot of people are using the same Build Agent with the same IP.

[sohail-dragon]

Temporary workaround:

1. Add this to top of your Podfile:
   source 'https://github.com/CocoaPods/Specs.git'
2. Remove Podfile.lock and Pods folder
3. Run pod install --repo-update

After that, you can push this changes to your repository.

Temporary work around worked for us but I understand it's not ideal. Still need to find a fix for the cdn.

[jimaek]

Can you please attach the HTTP headers when getting that error?
We definitely dont rate-limit, so I am guessing that error is proxied from the origin and we simply show it.

[slajar]

@jimaek how do I get those HTTP headers from cocoa pods?

[jimaek]

Yes it looks like a rate-limit on Github's side, the source of files for jsDelivr's CDN.
It seems like they only recently added it. I will try to contact them in case they could whitelist our IPs.
We will also try to add more IPs to our origin system to distribute the requests among them to avoid hitting Github's limits

[Albert221]

Looks like the problem is gone. Thanks!

[vandadnp]

The problem seems to have been resolved now for me too, thank you.

[budioktaviyan]

Yup, the problem has been solved for me too, could you please close the issue ?