could not find compatible versions for pod

Question

I am new in IOS development and git. I am having a problem after merging my local repo to the dev repo. After merging when I build the project I get an error in the Xcode that says, "The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation."

Build Error

I searched about this and tried the usual solution reinstalling the pods. But executing

pod install

I get another error in terminal that says

Terminal Error

At this point I tried deleting the files associated with the "FTPopOverMenu" pod and reinstalling with pod install. The error doesn't go away. Also, I tried solving it in this way - Error:“The sandbox is not in sync with the Podfile.lock…” after installing RestKit with cocoapods

But both error in the Xcode and in the terminal still remains. I'm new to IOS and Git. I really don't understand what is really happening here.

have you define a version for FTPopOverMenu in your pod file so check it(pod 'FTPopOverMenu', '~> 1.3') if it is not match with cocoa pod version or else try this "pod deintegrate" and "pod install" and "pod update" if any issue so let me know — Ravi Panchal, Feb 06 '18 at 08:02
I did the first-bit _try this `pod deintegrate` and `pod install`_ but the same error came up when I executed the `pod install`. I don't know what happened but the `pod update` fixed it. After deintigrating the `pod update` installed all the pods. No more pod error though. Thanks, man. — Somoy Das Gupta, Feb 06 '18 at 10:12
as per my guess you are working on an old project means which is already developed in Xcode 8 series and now you are working with latest Xcode and you have updated the code accordingly. and can i post my answer so it might help to other user ? — Ravi Panchal, Feb 07 '18 at 05:20

score 69 · Accepted Answer · edited Jan 28 '21 at 09:35

As per my guess you are working on an old project means which is already developed in Xcode 8 series and now you are working with latest Xcode and you have updated the code accordingly.

So just do the below steps:

"pod deintegrate"
"pod install"
"pod update" (if it is necessary so do it else if you have all latest pod so don't use it.)

It will remove all old cocoapods traces.

OR Alternate way to do it (Temp Work Around)

Remove that cocoa pod temporary, after all your work finish add to your project and give a try cause in my case it is the only work around i have that worked.

I did a combo between your answer and @Sardorbek Rkh – OhadM Jul 01 '20 at 13:52 — OhadM, Jul 01 '20 at 13:52

score 47 · Answer 2 · answered Oct 25 '18 at 15:00

47

In my case pod repos were outdated, solved with pod repo update

answered Oct 25 '18 at 15:00

landonandrey

1,271
1
16
26

What if it's not helping? – atereshkov Feb 19 '20 at 10:21
1

this worked for me. After that I could run `pod install` – Kheder Sep 08 '21 at 09:59

Ankur Lahiry · Answer 3 · 2019-05-16T08:47:38.773

36

if @Ravi Panchal's answer can't solve your problem, it may be your pod repo is out dated

Solution:

pod install --repo-update

edited May 16 '19 at 08:47

answered Apr 29 '19 at 06:56

Ankur Lahiry

2,253
1
15
25

score 25 · Answer 4 · answered Nov 07 '19 at 07:52

First, check your Podfile.lock and make sure no conflict with the spec constraints.

I encounter this issue with strange pod dependency, and solve it by

1. remove Podfile.lock

2. pod install again

It just work like magic. I think it is a bug that cocoapods cannot solve this kind of constraints in Podfile.lock. Remove the old Podfile.lock can make it apply the new rule easily.

Shourob Datta · Answer 5 · 2022-11-13T19:38:15.013

8

In .podfile

changed the iOS version

platform :ios, '13.0' // Warning change by your desired

It worked

edited Nov 13 '22 at 19:38

answered Dec 02 '21 at 19:51

Shourob Datta

1,886
22
30

score 5 · Answer 6 · edited Sep 24 '21 at 14:24

5

In my case it worked after I changed iOS version from 8.0 to 9.0 in Target (not Project) settings >> General >> Deployment Info

edited Sep 24 '21 at 14:24

mfaani

33,269
19
164
293

answered Jun 17 '20 at 05:55

SardorbekR

1,388
3
18
33

score 5 · Answer 7 · answered Sep 11 '21 at 11:08

5

please check your podfile and update the platform to the appropriate version number

platform :ios, '11.0'

answered Sep 11 '21 at 11:08

Kingsley Akpan

213
3
3

In my case that was the trick because I updated to Flutter 3.3 and it's not compatible with iOS 10. Thx. – Rodolfo Gonçalves Sep 24 '22 at 13:51

score 2 · Answer 8 · answered Feb 06 '18 at 08:37

2

I had the same issue with FIRMessaging from cocoapods. I solved the issue by doing like following steps

Remove FTPopOverMenu from your podfile which can find in your project folder.
Open terminal and run pod install. You can see in terminal that FTPopOverMenu will be removing from your pods.
Now, again open your podfile and write this pod 'FTPopOverMenu'. Run pod install in terminal.

The error will go away from terminal.

answered Feb 06 '18 at 08:37

Himanth

2,381
3
28
41

I followed the solution @ravi.p gave. I tried to solve it in this way, but every time I did `pod install` the same error occurred. – Somoy Das Gupta Feb 06 '18 at 10:16
have you removed FTPopOverMenu from your podfile before installing – Himanth Feb 06 '18 at 11:23
yes. But [the error](https://i.stack.imgur.com/GhsGH.png) was still there. `pod deintegrate` removed all cocoapods traces. Then `pod update` installed everything again. `pod install` didn't work. I have had a similar problem with **JVFloatLabeledTextField** and I removed the JVFloatLabeledTextField Folder from the Pods in my project navigator and uninstalled it with `pod install`. But this time `pod install` was showing the same error. Even after doing deintegrate. – Somoy Das Gupta Feb 06 '18 at 13:30

Giang · Answer 9 · 2018-11-20T10:23:52.240

1

I fixed by a change to dynamic pod version.

And delete file Podfile.lock

edited Nov 20 '18 at 10:23

answered Nov 20 '18 at 03:26

Giang

3,553
30
28

score 1 · Answer 10 · answered Jan 04 '23 at 12:09

1

if you are facing this error in Flutter CocoaPods could not find compatible versions for pod

increase your minimum deployments
cd ios and then rm -rf Pods/ Podfile.lock ; pod install
flutter build ios

answered Jan 04 '23 at 12:09

Umer Waqas - Top rated dev

3,072
29
26

score 0 · Answer 11 · edited Oct 29 '20 at 11:01

0

Please check the line below in your Podfile. Please make sure it is commented. it works for me.

platform :ios, '9.0'

edited Oct 29 '20 at 11:01

ChamCham

484
1
8
19

answered Oct 07 '20 at 10:00

vikas prajapati

1,868
2
18
26

score 0 · Answer 12 · answered Nov 04 '20 at 07:23

I have an answer regarding this in the thread already. But this time my scenario was different. My co-worker accidentally updated the cocoa version from the stable to a beta version, while I was using the lower stable version. I wasn't interested using the beta version, so I didn't update.

As deleting podfile.lock is dangerous which leads to removing the Cocoapods traces, I just opened podfile.lock in editors like Sublime Text, and downgraded the pod which is causing the problem.

score 0 · Answer 13 · edited Sep 13 '21 at 02:54

0

Look at the iOS Deployment Target, make it 11.0 and then do

pod install

and it will be fixed

edited Sep 13 '21 at 02:54

m4n0

29,823
27
76
89

answered Sep 12 '21 at 23:22

Erald

21
3

could not find compatible versions for pod

13 Answers13

Linked