CDN: trunk Repo update failed - 12 error(s):
Solution 1
I have same issue like yours, I fixed it by running:
pod repo remove trunk
and then pod install
, once these are complete I ran pod update
and it updated everything.
Solution 2
CocoaPods offers the ability to use either git or CDN. CDN is the default but for those who it doesn't work you can always fall back to the previous git-based implementation by adding
To fix add git path on your podfile
.
source 'https://github.com/CocoaPods/Specs.git'
Sazzad Hissain Khan
Connect with me: LinkedIn Core technical expertise: Git, OOP, Java, iOS (Swift, Objective-C), Xcode, iOS Configurations, Android (Java, Kotlin), System Design, Application Architecture, Development Processes, Testability. Special interest: Information Theory, Astronomy, Probability, Theory of Relativity, Randomness I am a strong believer of simplicity and code clarity **Short Bio:** Throughout over 9 years of experience on mobile software development, I have acquired a deep understanding on how to overcome the real hurdles of developing performant, robust, testable and maintainable applications from the requirement analysis to the architecture, design, development, continuous integration and continuous deployment. I have a strong fascination for CLEAN coding and SOLID principles. Problem solving is my passion regardless if its design related or architectural and I value the passion for problem solving minds. Usability, especially user intuitive and interactive UX for front ends and fault tolerance for backends are my prime concerns on developing any product. More importantly I enjoy Software Engineering and solely believe that this profession suits best for me.
Updated on December 24, 2022Comments
-
Sazzad Hissain Khan over 1 year
Getting error when I tried to update pod,
pod update
Error found,
[!] CDN: trunk Repo update failed - 12 error(s): CDN: trunk URL couldn't be downloaded: https://cdn.jsdelivr.net/cocoa/Specs/9/b/5/FBSDKCoreKit/6.1.0-alpha/FBSDKCoreKit.podspec.json Response: Timeout was reached
However, I can access the json path smoothly from my browser.
How to resolve this?