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 repo update crash on 1.8.x #9216
Comments
hmmmmmm can you list out exactly all steps you do from a clean CocoaPods install? You may have found a bug.
|
Yeah, is a bug, there is no way of setting up the local copy on cocopadods 1.8.x, but it will try to use it if you have the github url in the Podfile. |
@jcesarmobile so I can't reproduce your issue. It seems you might be hitting this issue #9209 Can you paste your |
See #9226 for why this is happening. |
Workaround: At least one invocation of |
cc @igor-makarov should we add this to create |
PR #9234 is out for review and will ship with 1.8.4. I reproduce'd the issue locally as well. |
Thanks for the fix, and sorry for not answering, I missed the notifications. Also my problem was on a private CI that was downgraded to 1.7.x because of this, so was hard to reproduce again. |
It's OK. There were other duplicate reports of this issue and I was able to figure it out. |
@dnkoutso is there a schedule for when this fix will be released in 1.8.4? |
Shipped today with 1.8.4 |
Report
I know CocoaPods 1.8 use the CDN by default, but since
pod setup
does nothing, if you have a Podfile withsource 'https://github.com/CocoaPods/Specs.git'
, when you runpod repo update
it will fail.pod setup
should continue working or there should be a new command to get the git based source downloaded.What did you do?
I have an autogenerated Podfile with
source 'https://github.com/CocoaPods/Specs.git'
, when I runpod repo update
it fails.What did you expect to happen?
To get the git sources as on previous versions
What happened instead?
Got this error:
No such file or directory ~/.cocoapods/repos/Spec_Lock
CocoaPods Environment
Stack
Plugins
The text was updated successfully, but these errors were encountered: