The version of CocoaPods used to generate the lockfile (1.5.3) is higher than the version of the current executable (1.5.2)

Question

on $pod install it gives warning & fails

The version of CocoaPods used to generate the lockfile (1.5.3) is higher than the version of the current executable (1.5.2)

What is it trying to say ?

macOs : 10.11.6 osx el capitan

my pod version is : 1.5.3

What does"current executable" (1.5.2) means ?

and

how to update it ?

You will need to update your pod. – Krishna Datt Shukla Jul 06 '18 at 07:55 — Krishna Datt Shukla, Jul 06 '18 at 07:55

score 85 · Accepted Answer · answered Jul 06 '18 at 17:55

85

The error you are getting is due to your podfile.lock being built with an older version of Cocoapods. All you need to do is to delete your podfile.lock file and run pod install. This will create a new podfile.lock, with your current dependencies. Note that it should not take too long because your files should already be downloaded, they just need to be linked in said file.

answered Jul 06 '18 at 17:55

Jstngoulet

1,055
7
12

I don't know if this was just an issue for me or but the `podfile.lock` but while it was being tracked through git it wasn't part of the Xcode project so I had to delete it through terminal. – mfaani Sep 08 '19 at 16:35
1

@Honey the Podfile.lock is usually not included in your Xcode file structure, but can usually be found in your project's root directory in Finder – Jstngoulet Sep 09 '19 at 17:52
4

Careful, this has the unintended consequences of upgrading all of your pods if you had not version locked them in your Podfile. – DiggyJohn Apr 16 '20 at 12:36
It didn't resolved to me.. – saddam May 02 '22 at 04:17
I tried the above suggestion and check the pod version, it still remains the same. – Antony Aug 08 '22 at 04:22
@DiggyJohn If following best practices of [12 factor apps](https://12factor.net) you would not run into this issue. However, you are correct if they are not explicitly declared. – Jstngoulet Mar 07 '23 at 20:51

vijay · Answer 2 · 2023-01-31T17:02:11.187

19

3 solution

deleted ios/podfile.lock and again do $pod install

OR

OS UPDATE

2.1 updated mac to high sierra or higher

2.2 update xcode

2.3 then update pod $sudo gem install cocoapods

2.4 then $cd ios

2.5 then $pod install

OR

do any thing to make version match, then only it will work

edited Jan 31 '23 at 17:02

answered Jul 06 '18 at 16:48

vijay

10,276
11
64
79

Tried both answers and neither are working for me...any other ideas? – Joshua Hart Aug 09 '19 at 00:26
@JoshuaHart do all the things to make version match, then only it will work , I only remember 2 – vijay Aug 09 '19 at 07:00
@JoshuaHart, if nothing else works, try a pod deintegrate and then a pod install. – Derryl Thomas Dec 13 '19 at 11:02

Pranav Pravakar · Answer 3 · 2020-09-19T12:02:24.070

6

For those like me whose cocoapods version is 1.5.2, you can update cocoapods using

sudo gem install cocoapods

and the problem is solved

For checking pod version use

pod --version

For those for which cocoapods version is 1.5.3, you can delete podfile.lock and do pod install. However please note that if the version, of libraries used in your project, is not specified in podfile, then they will be automatically updated to latest vesrion.

edited Sep 19 '20 at 12:02

answered Sep 19 '20 at 11:57

Pranav Pravakar

205
3
7

`sudo gem install cocoapods` worked for me. Thanks! – daniel galarza Sep 14 '22 at 22:50

score 1 · Answer 4 · answered Dec 28 '19 at 22:13

1

$ [sudo] gem install cocoapods

you can update with this command

answered Dec 28 '19 at 22:13

Ali Murat

131
5

1

Welcome to Stack Overflow. When answering an older question with existing answers it is useful to point out what new aspect of the question your answer addresses. It appears that your answer was already included by one of the other existing answers. – Jason Aller Dec 29 '19 at 03:55

score 0 · Answer 5 · answered Apr 14 '22 at 00:40

0

If you have tried the above methods and it doesn't work, then try this way:

gem update --system

answered Apr 14 '22 at 00:40

quynhbkhn

59
4

Ahmad Khudeish · Answer 6 · 2023-03-01T01:24:49.880

Had the same issue, I updated my cocoacpods version and it worked.

If you previously installed cocoapods using brew

You need to update your local installation of cocoapods, you can run:
```
 brew install cocoapods 
```
Once installed hen run
```
pod install
```

If you previously installed cocoapods using gem:

You need to update your local installation of cocoapods, you can run:
```
 sudo gem install cocoapods 
```
Once installed you can generate your new Podfile.lock matching the new version by running:
```
pod install
```

You might have to also sometimes upgrade your ruby version if it does not work with the cocaopods version you installed you can use rbenv to upgrade your ruby version to the one compatible with your cocaopods.

score -2 · Answer 7 · answered Aug 20 '20 at 07:52

-2

$ sudo gem install cocoapods

you can solve

answered Aug 20 '20 at 07:52

wayne214

1

Please highlight the additional insight this answer provides, in comparison to existing older answers. Currently it gives an impression of only repeating the code of a different answer, but with even less explanation. The helpfulness of this answer is hence quite non-obvious. – Yunnosch Aug 20 '20 at 08:14
Welcome to Stack Overflow. Code-only answers are discouraged on Stack Overflow because they don't explain how it solves the problem. Please edit your answer to explain how this line solves the problem and how it improves on the existing upvoted answers the question already has, so that it is useful for users with similar issues. – FluffyKitten Aug 20 '20 at 09:12

The version of CocoaPods used to generate the lockfile (1.5.3) is higher than the version of the current executable (1.5.2)

7 Answers7

Linked