Cocoapods: The `master` repo requires CocoaPods 1.0.0 - (currently using 0.39.0)

Created on 13 Nov 2016  Â·  17Comments  Â·  Source: CocoaPods/CocoaPods

I run sudo gem update cocoapods

but it says:

Updating installed gems
Nothing to update

What should I do now? Please help me. Thanks.

Most helpful comment

Is 0.39.0 broken? We have several reasons for not upgrading to 1.0.0 yet.

All 17 comments

gem install cocoapods:1.1.1

I run pod setup ,

it says:

[!] The `master` repo requires CocoaPods 1.0.0 -  (currently using 0.39.0)
Update CocoaPods, or checkout the appropriate tag in the repo.

When I run gem install cocoapods:1.1.1 , it says successfully installed cocoapods-1.1.1

When I run pod --version, it says 0.39.0

What should I do now? Please help me. Thanks.

what does pod _1.1.1_ version give you?

I run pod --version, it only says 0.39.0

That's odd. What does gem env and which pod give you? Seems like a RubyGems issue to me :/

Does backward compatibility for 0.39.0 just has been dropped?

In addition to update, I have no choice but to.....

除了更新,我别无他法。

Is 0.39.0 broken? We have several reasons for not upgrading to 1.0.0 yet.

pod --version
1.2.0.beta.1
Thanks @segiddins

This blog post explain and solve the issue for me.
http://blog.cocoapods.org/Sharding/

I uninstalled pod and reinstalled it. It works.

I have also faced same issue that after updating cocoapods using command $ gem install cocoapods:1.1.1, is still telling me the same version 0.39.0.
I used $ gem uninstall cocoapods and then it ask me which version I want to uninstall. I choose cocoapods-0.39.0 and got message Successfully uninstalled cocoapods-0.39.0 and now it returns 1.1.1 on command $ pod --version

I've updated the blog post with some recommendations that allow you to keep using 0.39 and below: https://github.com/CocoaPods/blog.cocoapods.org/pull/140

sudo gem install -n /usr/local/bin cocoapods

I just had to sudo gem update cocoapods

Same problem, updated to cocoapods 1.3.1, but pod --versions, shows 0.39.0
It seems like rbenv shims problem, try running rbenv rehash. Solved it for me.

Was this page helpful?
0 / 5 - 0 ratings