CocoaPods / CocoaPods

The Cocoa Dependency Manager.
https://cocoapods.org/
Other
14.47k stars 2.62k forks source link

trunk URL couldn't be downloaded: https://cdn.jsdelivr.net #12370

Open cherpake opened 1 month ago

cherpake commented 1 month ago

Expired certificate

CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/1/e/b/SDWebImageSwiftUI/3.0.3/SDWebImageSwiftUI.podspec.json Response: SSL peer certificate or SSH remote key was not OK

Jenarath commented 1 month ago

Same issue

[!] CDN: trunk Repo update failed - 220 error(s): CDN: trunk URL couldn't be downloaded https://cdn.jsdelivr.net/cocoa/Specs/0/3/5/Firebase/1.0.0/Firebase.podspec.json Response: SSL peer certificate or SSH remote key was not OK

Screenshot 2024-05-02 at 12 22 42 PM
cherpake commented 1 month ago

I changed the source to GitHub in the Podfile to solve this issue

VinhShin commented 1 month ago

Same issue

thuyydt commented 1 month ago

same here [!] CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/0/3/5/Firebase/10.25.0/Firebase.podspec.json Response: SSL peer certificate or SSH remote key was not OK

turkcankeskin commented 1 month ago

Hello,

I normally expected this to be very easy but it doesn't work

How can I change the default registry address in cocoapods? It's very easy in npm "npm config set registry URL" but how does it work in pod?

https://twitter.com/aliveforms/status/1785911331226284250

We need to use https://fastly.jsdelivr.net/, but how? :/

@segiddins @fabiopelosin

km-steve-ham commented 1 month ago

Fix this quickly please! 'pod trunk push MyCocoaPod.podspec' (MyCocoaPod, example name) worked yesterday but now it doesn't. I need to release a hotfix quickly but CocoaPods is slowing me down by a lot. Log:

[!] CDN: trunk Repo update failed - 159 error(s):
CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/0/a/f/GTMOAuth2/1.1.0/GTMOAuth2.podspec.json Response: Couldn't resolve host name
…
CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/5/1/e/Charts/2.1.3/Charts.podspec.json Response: Timeout was reached
…
CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/9/3/0/FirebaseMLCommon/0.15.0/FirebaseMLCommon.podspec.json Response: SSL peer certificate or SSH remote key was not OK
TrustDec commented 1 month ago

This way is not solved for me.

1- At the top of the Podfile add this line source 'https://github.com/CocoaPods/Specs.git' 2- Remove the Podfile.lock file 3- pod repo remove trunk 4- pod install

Got this solution from here (https://github.com/CocoaPods/CocoaPods/issues/11939)

turkcankeskin commented 1 month ago

This solved issue for me.

1- At the top of the Podfile add this line source 'https://github.com/CocoaPods/Specs.git' 2- Remove the Podfile.lock file 3- pod repo remove trunk 4- pod install

Got this solution from here (#11939)

No I don't think this will work. Can you check from which address you downloaded the pod packs? Because if it is still using https://cdn.jsdelivr.net, the error will continue.

km-steve-ham commented 1 month ago

I'm trying to release my CocoaPods, MyCocoaPod.podspec, by typing 'pod trunk push MyCocoaPod.podspec'. I'm not trying to install a CocoaPod, so I think Podfile or Podfile.lock are irrelevant for me.

abdallahrida commented 1 month ago

Same issue here !!

CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/0/3/5/Firebase/9.6.0/Firebase.podspec.json Response: SSL peer certificate or SSH remote key was not OK

abdallahrida commented 1 month ago

I changed the source to GitHub in the Podfile to solve this issue

Can you explain how to do it? What do you include in the Podfile?

TrustDec commented 1 month ago

Now the stupidest way is to manually download https://github.com/CocoaPods/Specs.git and move the decompressed Specs directory to the /Users/username/.cocoapods/repos/trunk/ directory, which can be solved, but the download and decompression movement is very slow.

This process took about half an hour, and now I have successfully run pod install 🤣

abdallahrida commented 1 month ago

Now the stupidest way is to manually download https://github.com/CocoaPods/Specs.git and move the decompressed Specs directory to the /Users/username/.cocoapods/repos/trunk/ directory, which can be solved, but the download and decompression movement is very slow.

This process took about half an hour, and now I have successfully run pod install 🤣

I am trying to clone https://github.com/CocoaPods/Specs.git it gave this error remote: Enumerating objects: 6837333, done. remote: Counting objects: 100% (5436/5436), done. remote: Compressing objects: 100% (2930/2930), done. error: 6765 bytes of body are still expected.58 MiB | 255.00 KiB/s fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output

TrustDec commented 1 month ago

Now the stupidest way is to manually download https://github.com/CocoaPods/Specs.git and move the decompressed Specs directory to the /Users/username/.cocoapods/repos/trunk/ directory, which can be solved, but the download and decompression movement is very slow. This process took about half an hour, and now I have successfully run pod install 🤣

I am trying to clone https://github.com/CocoaPods/Specs.git it gave this error remote: Enumerating objects: 6837333, done. remote: Counting objects: 100% (5436/5436), done. remote: Compressing objects: 100% (2930/2930), done. error: 6765 bytes of body are still expected.58 MiB | 255.00 KiB/s fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output

I use Safari to download ZIP.

hieunt130220 commented 1 month ago

fixed now

abdallahrida commented 1 month ago

fixed now

how ?

hieunt130220 commented 1 month ago

fixed now

how ?

It has been fixed

km-steve-ham commented 1 month ago

I went to https://www.jsdelivr.com/about and reported to Dmitriy Akulov (Founder) through X. He replied:

Hey, the issue is now resolved. For some reason Cloudflare replaced our certificate with an old expired one. We dont know yet why they did that. But we removed them completely from our CDN until we understand what happened.