Error: "The sandbox is not in sync with the Podfile.lock..." after installing RestKit with cocoapods

K

60

367

I've encountered an strange issue after installing RestKit with cocoapods. after resolving RestKit dependency for my project with cocoapods and trying to build it, I face this error:

The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

I tried running pod install, but no change.

Here are some shots: enter image description here

enter image description here

  PODS:
  - AFNetworking (1.3.3)
  - RestKit (0.20.3):
    - RestKit/Core
  - RestKit/Core (0.20.3):
    - RestKit/CoreData
    - RestKit/Network
    - RestKit/ObjectMapping
  - RestKit/CoreData (0.20.3)
  - RestKit/Network (0.20.3):
    - AFNetworking (~> 1.3.0)
    - RestKit/ObjectMapping
    - RestKit/Support
    - SOCKit
  - RestKit/ObjectMapping (0.20.3)
  - RestKit/Search (0.20.3):
    - RestKit/CoreData
  - RestKit/Support (0.20.3):
    - TransitionKit (= 1.1.1)
  - RestKit/Testing (0.20.3)
  - SOCKit (1.1)
  - TransitionKit (1.1.1)

DEPENDENCIES:
  - RestKit (~> 0.20.0)
  - RestKit/Search (~> 0.20.0)
  - RestKit/Testing (~> 0.20.0)

SPEC CHECKSUMS:
  AFNetworking: 61fdd49e2ffe6380378df37b3b6e70630bb9dd66
  RestKit: 1f181c180105a92f11ec4f6cd7de37625e516d83
  SOCKit: 2f3bc4d07910de12dcc202815e07db68a3802581
  TransitionKit: d0e3344aac92991395d4c2e72d9c5a8ceeb12910

COCOAPODS: 0.29.0

Kissee answered 26/1, 2014 at 17:11 Comment(10)

Did you try Run 'pod install' or update your CocoaPods installation. as suggested by the error? – Iterative 26/1, 2014 at 17:13

absolutely, I did that, but no success – Kissee 26/1, 2014 at 17:26

Can you post the version of Restkit in the Podfile.lock and in Pods/Manifest.lock? That error occurs when these are not the same. – Lactone 27/1, 2014 at 2:22

yeah, I compared them, they are exactly identical. – Kissee 27/1, 2014 at 14:54

The error above the "sandbox" error is "diff: command not found" I don't know if reinstalling diff could fix the problem, but it may be a hint as to what's happening. – Corked 9/2, 2014 at 2:28

I couldn't find any solution. Finally I added manually – Kissee 9/2, 2014 at 16:18

@cesarferreira I mean I had to install RestKit manually without using cocoPods. – Kissee 18/3, 2014 at 18:24

To begin with, you need to understand 1. What the Podfile.lock is. 2. Then what the Manifest.lock file is. I've explained them in detail in my answer. See here – Kentiga 18/1, 2021 at 23:3

Please delete the Pods folder and Podfile.lock file then run pod install. Finally Clean + Build + Archive. I hope it will work fine. – Restharrow 26/2, 2022 at 14:33

Look here: https://mcmap.net/q/93552/-flutter-on-ios-fatal-error-module-39-cloud_firestore-39-not-found (solution worked for me) – Packing 31/8, 2022 at 16:13

O

422

I was able to fix that by updating CocoaPods.

I. Project Cleanup

In the project navigator, select your project
Select your target
Remove all libPods*.a in Build Phases > Link Binary With Libraries

II. Update CocoaPods

Launch Terminal and go to your project directory.
Update CocoaPods using the command pod install

Oriel answered 5/4, 2014 at 8:0 Comment(13)

When I run the pod install command in the project directory I received below warning: The use of implicit sources has been deprecated. To continue using all of the sources currently on your machine, add the following to the top of your Podfile: source 'github.com/CocoaPods/Specs.git' I also added this link in the pod file but same thing happened. please suggest. – Vernonvernor 22/10, 2014 at 6:9

In addition to this I had to remove all CocoaPod related build phases such as 'Check Pods Manifest.lock' and 'Copy Pods Resources'. – Kalfas 19/12, 2014 at 19:52

Usually the issue happens because of this: github.com/CocoaPods/CocoaPods/issues/1822 – Enunciation 14/4, 2015 at 7:8

[!] No `Podfile' found in the project directory. getting this message in terminal – Restrain 10/8, 2015 at 10:3

@ Valery Pavlov These steps worked but after a successful project clean, the build fails immediately with the same 3 errors I cant seem to get rid of below. I tried fully removing all cocoapods, reinstalling, updating, doing all of this with xcode restarts and etc. All of these in terminal perform successfully but the build continues to fail. Any further thoughts? Errors: diff: /../Podfile.lock: No such file or directory diff: /Manifest.lock: No such file or directory error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation. – Azaleeazan 25/8, 2015 at 6:58

would be useful to have more clarity on step 1 and 3 ie what headings its under – Fluorinate 23/12, 2015 at 11:34

I tried Pod install..But i got error like this You have either: * out-of-date source repos which you can update with pod repo update. * mistyped the name or version. * not added the source repo that hosts the Podspec to your Podfile. Note: as of CocoaPods 1.0, pod repo update does not happen on pod install by default. – Kimber 7/6, 2016 at 12:37

@Mr. Fahrenheit, for me pod update works, are you sure that point 2.Update CocoaPods using the command pod install is correct, or you should update the command in your ans – Goulash 8/10, 2016 at 11:47

In my case, this work when uninstalling react-native package as well. – Prehensile 13/2, 2020 at 1:47

Hi, I tried everything from the answers of you and others, but I'm still getting the same error. My project is created form cordova. Is there any special care to be take from cordova, please let me know. – Baucis 7/7, 2020 at 9:12

@Kalfas you should not remove that script from the build phase. See here . That script is there to make sure you're snapsho of all dependencies is in sync with the snapshot of your repo. Or perhaps after you remove it, it gets added again – Kentiga 18/1, 2021 at 23:19

I am confused. The OP said he ran pod install, and your solution is to run pod install? – Terricolous 2/3, 2021 at 20:38

I resolved thad only by these commands in terminal: 1) cd ios 2) pod install . After that I selected 'Clean Build Folder' from 'Product' menu and everything goes OK. – Trepang 22/2, 2022 at 11:58

B

137

After many attemps I managed to fix this problem. Variable ${PODS_ROOT} was not set and I do below trick. Go to Build Phases -> Check Pods Manifest.lock and replace

diff "${PODS_ROOT}/../Podfile.lock" "${PODS_ROOT}/Manifest.lock" > /dev/null

to

diff "${SRCROOT}/Podfile.lock" "${SRCROOT}/Pods/Manifest.lock" > /dev/null

It helps me.

Baseless answered 24/6, 2015 at 11:32 Comment(5)

Why $PODS_ROOT is not setted up? Do I need to reinstall pods for my project? – Sheathing 3/11, 2015 at 13:33

The reason why $PODS_ROOT was not set is mainly because the .xcconfig file generated by cocoapods is not applied to the build target. – Septuagesima 26/7, 2016 at 5:37

@Septuagesima how do I apply a .xcconfig file? – Skuld 15/9, 2017 at 22:52

In my case I set PODS_ROOT = ${SRC_ROOT}/Pods in my xcconfig for the same effect. – Cloudcapped 6/5, 2020 at 20:33

that solved my problem for ionic Cordova project. – Fibrinogen 31/10, 2021 at 8:48

B

88

I had been searching for hours and I found solutions as follow:

In my case, method 1 works.

Method 1:

choose the target > go to Build Phases > click Link Binary With Libraries > remove all libPods.a files
open Terminal > direct to your project > run:
```
  pod install
```
clean and build project

ref.1

Method 2:

open Terminal > direct to your project > run:

 pod deintegrate --verbose    
 pod install --verbose

ref.2

Method 3:

choose the target > go to Build Settings > click "+" sign
add 2 User-Defined Settings: [to the left = to the right]
```
 PODS_ROOT = ${SRCROOT}/Pods
```

and

    PODS_PODFILE_DIR_PATH = ${SRCROOT}/

ref.3

Bobbibobbie answered 13/12, 2018 at 5:50 Comment(6)

I tried all other solutions but nothing worked. Method 3 worked for me. – Kushner 19/12, 2019 at 7:22

However... after resolving the problem byMethod 1 I came across with another error... Showing Recent Errors Only Command PhaseScriptExecution failed with a nonzero exit code – Lantha 28/11, 2020 at 7:48

Method 2 worked for me. Thank you very much. – Oblong 26/1, 2021 at 7:35

Method 1 worked for me, thanks ! – Lick 10/2, 2022 at 23:15

None of them working for me. It's a very old project and many coworkers have it up and running, and I had it working before it suddenly stopped. I don't believe it's something related to pod, despite the name – Yardmaster 22/2, 2023 at 15:11

Method 3 worked for me – Ander 17/5, 2023 at 11:30

M

47

If you remove all pods from your target in the Podfile, e.g.

target 'myTarget' do
pod 'great-stuff', '~> 4.0'  // you deleted this last pod
end

you'll need to manually delete these builds steps from your Xcode target Build Phases:

Check Pods Manifest.lock
Copy Pod resources

Cocoapods (current stable version 0.37.2) does not perform this cleanup when you run pod install.

Molding answered 7/7, 2015 at 9:20 Comment(2)

This worked for me. Id been migrating to swift 2 and had commented out all pods - i just turned one of the pods back on rather than messing with deleting build phases. – Interrex 30/9, 2015 at 17:23

bingo! i spent hours removing my workspace, reinstalling pods, etc and nothing else worked. – Journalist 29/10, 2015 at 4:4

D

41

Removing pods from the project and re-installing worked for me.

There is nice GitHub repository that can completely remove the pods from the project.

Just keep the backup of your PodFile and run below commands.

gem install cocoapods-deintegrate
gem install cocoapods-clean
Go to the project directory and run pod deintegrate
Again run pod clean
Run pod install

Clean and run.

Demijohn answered 15/4, 2016 at 12:44 Comment(8)

You are great, only yours worked for me, thanks a lot – Ease 26/7, 2017 at 19:34

After running these commands I get a successful build message, but now, nothing appears to run on the simulator nor the console. Do you know why this happened? – Surbased 21/8, 2017 at 2:39

BE AWARE: Build works, but the pod clean dissapeared the project target. No archives were generated nor app builded. – Brainpan 7/2, 2019 at 19:32

@Brainpan the disappeared content will regenerate on "pod install" again – Demijohn 8/2, 2019 at 9:25

Despite that, after doing the steps you mentioned my app icon don't appear anymore as the main project... Only the cordova logo appears, and no build or archive is being generated. – Brainpan 11/2, 2019 at 23:25

Its worked for me, I update my Xcode 12.3 and try to run flutter project I am not able after I did your steps its worked again Thanks – Hannahhannan 31/12, 2020 at 4:5

This solution worked for me, albeit it was not necessary to run “pod clean”. – Fari 18/11, 2021 at 16:49

Note: This still works in 2022 – Sarmiento 14/3, 2022 at 21:13

M

18

If you are seeing an error like the following:

diff: /../Podfile.lock: No such file or directory diff: /Manifest.lock: No such file or directory error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

Then there's a problem with Cocoapods in your project. Sometimes cocoapods can get out of sync and you need to re-initiate cocoapods. You should be able to resolve this error by:

Deleting the Podfile.lock file in your project folder
Deleting the Pods folder in your project folder
Execute 'pod install' in your project folder
Do a "Clean" in Xcode
Rebuild your project

Madlin answered 23/2, 2018 at 23:21 Comment(6)

Thank you so much. You made my day. Nothing else worked in my Flutter project. – Airliner 25/9, 2019 at 11:41

This is the only solution that worked for me as well. Deleting Podfile.lock. Be warned that you might get some unexpected version upgrades when doing this. – Seabee 3/3, 2020 at 22:15

for flutter: run pod install in your flutter_project/ios – Dich 18/4, 2020 at 11:9

@Seabee you should not remove delete the lock file as mentioned. To explain what's happening. See here . – Kentiga 18/1, 2021 at 23:22

Thanks @Honey, I did not know it at the time. Killing/overwriting the Manifest.lock would do the trick I guess =) – Seabee 20/1, 2021 at 21:55

This worked for me in my Flutter project! Thanks a lot! – Yam 7/9, 2021 at 18:36

A

14

After changing target name

My problem was xcconfig with old target names.

Went to project file -> info -> configuration
Removed old xcconfig (both Debug & Release)
pod install

It would update to new ones.

Also if you had missing .h files that's the reason (pods header search path is in these xcconfig)

Apiculture answered 3/2, 2016 at 14:54 Comment(1)

Choosing None worked for me as well. I was struggling with this for a day trying to integrate the Gimbal2 SDK into an Ionic4 project. – Periosteum 25/10, 2018 at 17:47

C

12

I found my solution: Run:pod update instead of pod install. The error was fixed!

Confabulate answered 23/2, 2017 at 3:16 Comment(1)

Well. This will update outdated pods, so be sure that that is what you want. – Pounce 30/9, 2019 at 13:8

K

12

First you have to understand what the Podfile.lock is then understand what the Manifest.lock is and where it's used.

The Podfile holds either the (optimistic or exact) versions of every dependency you have. The lock file holds only exact versions.

Once you do pod install all the pods get downloaded/installed into the /pods directory. You may want to commit them Or maybe not. That's up to your team. What's NOT up to your team is decide if they should commit the the Podfile.lock or not. That needs to be committed so every dev in the team can be sure they've got the exact same version.

So let's say you downloaded your team’s code. In your project's root directory you only have Podfile and Podfile.lock and the Pods directory wasn’t committed.
Then you do pod install to creat the Pods directory. Your snapshot of every pods’ version should match with the versions of all pods from the Podfile.lock.
CocoaPods has a safety check in place, to ensure matching versions

This is where the Manifest.lock comes into play. Manifest.lock is your local machine's lock created. It has to match with Podfile.lock that is generated by the last commit (that caused changes in for your pods) in your repo. If it doesn't match then something is messed up.

Docs on what the Manifest.lock file is:

  #     Manifest.lock: A file contained in the Pods folder that keeps track of
  #     the pods installed in the local machine. This files is used once the
  #     exact versions of the Pods has been computed to detect if that version
  #     is already installed. This file is not intended to be kept under source
  #     control and is a copy of the Podfile.lock.

I honestly can only think of one scenario in which the Manifest.lock and Podfile.lock would be out of sync:

I mean if you pull from main branch, then you get main's Podfile and lock file. If you then make a change to the Podfile and then run pod install, then you would be updating the Podfile.lock and Manifest.lock and will keep them in sync. No issues with this

Is this just so that if:

You and your team don’t commit the /Pods directory
You have merge conflicts in your Podfile or Podfile.lock but don’t realize it. Or you haven't committed both Podfile and Podfile.lock
Then given that Xcode doesn’t process the Podfile and Podfile.lock, then naturally your project can build successfully.
However if you go in an inspect your Build Phases of your targets you'd see the following

That script is documented here

#     Adds a shell script build phase responsible for checking if the Pods
#     locked in the Pods/Manifest.lock file are in sync with the Pods defined
#     in the Podfile.lock.
#     
#     @note   The build phase is appended to the front because to fail fast.
#     
#     @return [void]

What those lines do are: perform a diff and ensure that sure your Manifest.lock i.e. your local snapshot of all installed pod versions are equal to Podfile.lock i.e. your repo's current snapshot of all installed pod versions.

The fix is likely super simple, just make sure you Podfile is what you want. Then just run pod install. You have also somehow accidentally made changes to your Manifest.lock inside your /Pods directory (or as mentioned earlier maybe only committed the lock file but not the Podfile or vice versa). Deleting /Pods directory causes no harm. Just do a pod install after. Do not do pod update unless that's what you want.

Just make sure you never delete the Podfile.lock otherwise if you do pod install then it would update all dependencies to the latest version it can.

Also helpful to see and this video on lock files, CocoaPods docs on how the lock file is put to use differently for pod install vs. pod update and last see how all that logic is used in more detail this artsy blog on checksums. It's worth noting that a single space will create a new checksum and can make things out of sync.

Kentiga answered 18/1, 2021 at 23:2 Comment(2)

Did all of that didn't help. Pretty sure the test itself is buggy and produces a false failure. Not the first time I came across a sanity check which fails unnecessarily. There is a reason why I program sanity checks as WARNINGS and not as errors. – Parrie 3/3, 2021 at 10:31

@Parrie I'm skeptical if you're correct. However if you're 100% sure, you can remove the check from your project's build phase – Kentiga 3/4, 2022 at 14:30

E

11

Go to Build Phases -> Check Pods Manifest.lock
Replace

${PODS_ROOT}/Manifest.lock

with:

${SRCROOT}/Podfile.lock" "${SRCROOT}/Pods/Manifest.lock

Check in image :

Epexegesis answered 10/9, 2019 at 12:41 Comment(2)

This worked for me in a Cordova iOS build, while the accepted answer did not work. – Raul 8/11, 2019 at 10:14

Thank you for pointing out the origin of the error, but this also didn't solve my issue. Ideally Cordova do not recommend modifying their pod file, but if we delete the Podfile.lock and do a pod install again with the modified Podfile , there should not be an error. So, as a last option I commented the if condition, since I feel it is not a necessary check, and thus I came out of the issue. – Wieren 9/3, 2021 at 14:52

U

9

Can you try this:

Delete the Pods folder
Delete Podfile.lock
Run pod install
Clean + Build

Undesirable answered 4/1, 2022 at 18:43 Comment(0)

D

6

In my case, I got same error after integrating WatchKit app. To solve problem I needed to add both targets of WatchKit in Podfile:

target 'MyProject WatchKit App' do
    platform :watchos, '2.0'
    shared_pods
end

target 'MyProject WatchKit App Extension' do
    platform :watchos, '2.0'
    shared_pods
end

PS: Maybe this happened for me because I mistakenly installed pods for MyProject WatchKit App target initially.

Dateline answered 4/7, 2016 at 10:18 Comment(1)

I think you hit the nail on the head ;) – Insulin 31/10, 2016 at 20:57

D

6

Try to set up the correct target in Podfile and then run pod update or pod install

Deteriorate answered 16/12, 2019 at 22:16 Comment(0)

L

5

Run this, and your errors will vanish

rm -rf Pods && gem install cocoapods && pod install

Larrabee answered 19/7, 2019 at 18:45 Comment(0)

R

4

I encountered this issue with a misconfigured xcconfig file.

The Pods-generated xcconfig was not correctly #included in the customise xcconfig that I was using. This caused $PODS_ROOT to not be set resulting in the failure of diff "/../Podfile.lock" "/Manifest.lock", for obvious reasons, which Pods misinterprets as a sync issue.

Reverberatory answered 18/1, 2016 at 1:15 Comment(0)

B

4

For me the problem was that I made a new target in my app by duplicating an existing one, but forgot to add the target to the Podfile. For some reason, the cloned target did work for days without problems, but after a while it failed to build by this error. I had to create a new target entry for my cloned project target in the Podfile then run pod install.

Botti answered 2/9, 2016 at 10:46 Comment(0)

O

4

If you download the project from github or copy from other place, then the dependencies library do not exists, there will be this issue.

You just need to cd to the project/project_name directory in terminal , use ls to check whether there is a Podfile file.

if there exists the Podfile, you just need to install the dependencyies:

pod install

Ox answered 14/1, 2018 at 2:28 Comment(2)

Thanks - this really helped me a lot when I was running the flutter examples downloaded from their github website and I had received the same error. I navigated to the ios folder for each flutter example folder and did the pod install and then the flutter app worked. – Werra 13/4, 2018 at 9:12

glad to help you. – Ox 13/4, 2018 at 9:45

A

4

My working answer is:

Install update your cocoapods by this command: pod update
Install your new pods by this command. pod install
Last one command: sudo gem install cocoapods.

Aflutter answered 7/4, 2019 at 17:58 Comment(0)

A

3

This made my day!

Deleting the Podfile.lock file in your project folder
Deleting the Pods folder in your project folder
Execute pod install in your project folder
Do a "Clean" in Xcode
Rebuild your project

Abortionist answered 31/5, 2016 at 19:36 Comment(1)

I approve this message! Also if you're on Flutter don't forget to flutter pub get – Dich 27/5, 2020 at 19:13

F

3

The steps that worked for me (XCode 8.3.3/XCode 9 beta with a Swift 3.1 project)

 - Navigate to your project directory
 - pod install //which then asks you to do the next step
 - pod repo update //takes a while to update the repo
 - pod update
 - pod install
 - Close Xcode session
 - Open and Clean the project
 - Build/Run

Also make sure you open the .xcworkspace file rather than the project file (.xcodeproj) when working with pods. That should solve any errors with linking such as "Apple Mach -O Linker command failed"

Fibrilla answered 9/9, 2017 at 5:31 Comment(0)

K

3

Please do the following steps:

1: Deleting the Podfile.lock file in your project folder

2: Deleting the Pods folder in your project folder

3: Execute 'pod install' in your project folder

4: Do a "Clean" in Xcode

5: Rebuild your project

Kimber answered 20/7, 2018 at 11:52 Comment(0)

T

3

I tried everything, but the problem persisted. After that I did this and it worked ASAP (As Smooth As Possible).

Open the .xcworkspace file.
Change to legacy build system if using Cordova on Xcode 10.
Go to target/project of Podfile. Select Deployment traget as 11+
Then Change the debug and release to Pods-.build/release. It was App.debug/release in my case.Pic attached. Hope it helps.

Teratism answered 24/12, 2018 at 3:3 Comment(0)

A

3

Completely nothing worked out for me from these answers. Had to create the project again by running cordova platform add ios. What I've noticed, even freshly generated project with (in my case) Firebase pods caused the error message over and over again. In my opinion looks like a bug for some (Firebase, RestKit) pods in Xcode or CocoaPods. To have the pods included I could simply edit my config.xml and run cordova platform add iOS, which did everything for me automatically. Not sure if it will work in all scenarios though.

Edit: I had a Podfile from previous iOS/Xcode, but the newest as of today have # DO NOT MODIFY -- auto-generated by Apache Cordova in the Podfile. This turned on a light in my head to try the approach. Looks a bit trivial, but works and my Firebase features worked out.

Alfreda answered 19/4, 2020 at 14:5 Comment(1)

This is the only method that worked for me. Tried all others. I deleted platforms and did a reinstall of 'cordova platform add ios'. I too think I had a previous platforms/ios which I used on a previous version of xcode. – Mattland 23/6, 2020 at 21:4

M

3

Check Pods target and Runner target thats have to be same

1- Runner

2- Pods

Mc answered 23/6, 2021 at 10:10 Comment(0)

C

2

For me, working in flutter, the configuration was not automatically added due the existing configuration.

Adding #include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig" to Flutter/Release.xcconfig and Flutter/Debug.xcconfig

solved the issue.

Chisholm answered 23/1, 2019 at 14:2 Comment(0)

N

2

Be sure the pod configuration files are set.

Nagari answered 29/4, 2021 at 8:51 Comment(0)

N

1

When you do

pod install --verbose

make sure:

1- you are in the correct directory. Most times, when a github project is downloaded, there will be a master folder. You need to be inside the actual project name folder(masterfolder/project folder) in the terminal before you invoke pod install --verbose

2- Delete the old pod lock folder then clean the project using xcode clean & do pod install.

3- Keep your rvm updated.

Necessitate answered 31/7, 2016 at 8:21 Comment(0)

T

1

My problem was the cocoa pods version so I installed the latest with: sudo gem install cocoapods --pre Then pod update

That worked for me

Tighten answered 29/6, 2017 at 15:11 Comment(0)

E

1

If you are applying to the way Project Cleanup and your project still error.

You can go to tab Build Phases and then Find Check Pods Manifest.lock and remove the script.

Then type command to remove folder Pods like that rm -rf Pods

and then you need to remove Podfile.lock by command rm Podfile.lock

Probably, base on a situation you can remove file your_project_name.xcworkspace

Finally, you need the command to install Pod pod install --repo-update.

Hopefully, this solution comes up with you. Happy coding :)

Ellison answered 24/11, 2017 at 7:18 Comment(1)

@Kalfas you should not remove that script from the build phase. See here . That script is there to make sure you're snapsho of all dependencies is in sync with the snapshot of your repo. Or perhaps after you remove it, it gets added again – Kentiga 18/1, 2021 at 23:23

Y

1

I had same error. First I update cocoapods using

sudo gem install cocoapods

then install pods using Pod install command worked for me.

Yeung answered 5/6, 2018 at 11:50 Comment(0)

K

1

I faced this problem in a Flutter project. I just opened iOS Module in xCode and Build Clean Folder worked for me.

Kadi answered 18/9, 2019 at 7:52 Comment(0)

B

1

I had the same issue with Ionic-3, I did some above mention steps but none of them worked for me.

For Ionic Remove the ios platform

$ ionic cordova platform remove ios
$ ionic cordova platform add ios

Open xcode then try to build. this worked for me :-)

Burnet answered 14/3, 2020 at 9:34 Comment(0)

W

1

Fixed my issue with ionic app by installing cordova version 9, tried all above solution mostly linked with xcode neither worked for my ionic app

If anyone facing same issue with their cordova app kindly update to cordova 9 to fix this

Warenne answered 28/4, 2020 at 13:56 Comment(0)

B

1

This can also happen if you use Windows for the Git checkout, and the Podfile.lock is created with windows (CRLF) line endings.

Baize answered 8/2, 2021 at 9:13 Comment(0)

E

1

I solved by running pod install and copying the content of file Pods/Manifest.lock to the file Podfile.lock

Extinctive answered 10/4, 2022 at 9:50 Comment(0)

S

1

Following the answer of Mr. Fahrenheit what helped me to solve the problem on mac m1, instead of pod install was to run:

sudo arch -x86_64 gem install ffi
arch -x86_64 pod install

instead of pod install

Simonesimoneau answered 14/9, 2022 at 8:33 Comment(1)

This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review – Antitank 20/9, 2022 at 12:29

C

0

if your pods are empty

remove copy pods resources and check pods manifest.
lock from build phases settings of your project

Campanulaceous answered 7/12, 2015 at 11:19 Comment(0)

T

0

My problem was when my fellow developer added a pod in the project and then i pull the project using github then the error occurred. I ran pod install and it updated the pods with new library which was added by my fellow developer. hope it helps.

Triage answered 9/3, 2016 at 6:30 Comment(0)

S

0

I have the same problem with latest ComponentKit 0.14. The reason is PODS_ROOT was not set and i have found the solution is add a line to ComponentKit.xcconfig :

#include "../Pods/Target Support Files/Pods-ComponentKit/Pods-ComponentKit.debug.xcconfig"

Stegman answered 7/6, 2016 at 4:46 Comment(0)

M

0

Check in your project that Pods are maybe not being pushed to Git. So it's obvious that compile will break since it cannot find the Pods directory

 diff "${PODS_ROOT}/../../Podfile.lock" "${PODS_ROOT}/Manifest.lock" > /dev/null

I solved this by issuing pod install in the Terminal after navigating to my project's directory.

Indeed, I had an error cannot find pod command which meant that cocoapods were not installed. This is fixed via gem install cocoapods. If you get any dependency error, just install each command that is reported missing. In my case I had to update Ruby and after that cocoapods were installed properly and I was able to use the command pod install.

PS. If you have Pods directory, try pod update. Maybe your library needs updating.

Meeks answered 8/8, 2016 at 12:22 Comment(0)

H

0

i had this issue when i was trying to remove previously installed library

@Michal's answer helped me

Remove or uninstall library previously added : cocoapods

Harmonic answered 20/12, 2016 at 9:23 Comment(0)

D

0

I accidentally removed and then unpack back folder from where I tried to install pod.
It was like this: 1) cd in your project folder 2) zip your project 3) remove project folder 4) unzip folder back 5) from now even you have this folder you should go to this folder again from the terminal

Disillusion answered 13/4, 2017 at 11:25 Comment(0)

L

0

I had error:

diff: /../Podfile.lock: No such file or directory diff: /Manifest.lock: No such file or directory error: The sandbox is not in sync with the Podfile.lock.

I pulled request from bitbucket for first time. I cleaned my project and tried everything(pod install, pod update etc.) but none of the above answer worked for me. Then I just check the path where I was installing the pod and corrected it and installed again,It just worked. Make sure give the path just before where .xcodeproj or .xcworkspace(if it is already there)exist. May be someone get benefitted from this.

Likable answered 4/5, 2018 at 10:55 Comment(0)

D

0

I use the cocoa pods installation from the bundle.

Install bundler
Add Gemfile in root of project
Add required gems in Gemfile
bundle install
and then always use bundle exec pod install

If you don't know how-tos of one of these steps, searching on google will help :)

Delossantos answered 15/8, 2018 at 13:0 Comment(0)

O

0

pod deintegrate <PROJECT>.XCODEPROJ // will deintegrate cocoapods
pod install // installs the pods

Overburden answered 2/11, 2018 at 15:20 Comment(0)

I

0

I had the same issue I update everything to the latest from: npm -v 6.4.1 node -v v10.2.1 pod --version 1.5.3

to: npm -v 6.5.0 node -v v11.8.0 pod --version 1.6.0

and fix it

Ineffaceable answered 6/2, 2019 at 17:20 Comment(1)

Welcome to SO, you could take the tour here and your answers will be always appreciated. Even though your answer might be relevant, its a bit confusing as per how you guessed the mentioned versions as there is not any specific comment on that. Also your answer is not quite helpful as its missing the actual root cause you faced, plus your environment details and which steps you executed to fix the issue. – Garald 6/2, 2019 at 18:7

D

0

I got this error when I added a new developer account. I changed the Team under project name but I missed to update it under the Pods folder.

I solved it once I updated the new developer ID under the Teams option available under Pods-> Signing -> Team, the error was gone and the build succeeded.

Diagnosis answered 3/11, 2020 at 4:48 Comment(0)

E

0

I mixed up some comments above and that resolved my problem

I. Project Cleanup

In the project navigator, select your project
Select your target
Remove all libPods*.a in Build Phases > Link Binary With Libraries

II. Clean build folder

In XCode: Menu Bar → Product → Product -> Clean build Folder

III. Update cocapods

Run pod update

Endpaper answered 7/12, 2020 at 4:12 Comment(0)

A

0

For me it was an issue with the Ruby version number.

I was getting the error:

The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

After trying a million things, including much of what is included in this thread I wound up hacking the pod file located at: usr/local/bin/pod

I corrected the first line to point to the ruby version that actually existed on my machine. I changed:

#!/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby

to

#!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby

After days of struggling, changing a 3 to a 6 fixed everything.

Agnate answered 19/3, 2021 at 21:27 Comment(0)

B

0

I tried all sorts of combinations of pod install, deleting node_modules & reinstalling, cleaning & rebuilding the xcode project, and even restarting my computer. None of these worked for me...

The fix for me was running pod --version in my project's root directory. I don't know how or why, but this successfully installed a missing dependency, so I thought I'd share it here in case it helps someone else :)

Bandstand answered 21/4, 2021 at 10:19 Comment(0)

C

0

I was able to fix this by clicking Product->Clean Build Folder.

Crossway answered 21/5, 2021 at 3:48 Comment(0)

H

0

These simple steps work for me:

close your workspace
run pod install --repo-update
open your workspace, rebuild (It will be more reasonable, if you clean up your build folder).

Hesson answered 24/5, 2021 at 3:22 Comment(0)

T

0

In my case, this problem was due to a corrupt *.xcworkspace file. It was showing two different versions of my project in the Project Navigator menu on the left.

To verify, I removed the output redirection ( > /dev/null) from the bash script located in Build Phases > Check Pods Manifest.lock, so that it would print the diff to STDOUT. Sure enough, reading the build log, I had wildly different Podfile.lock and Manifest.lock output.

To fix it I deleted my *.xcworkspace, then ran pod install again from my ios folder. That autoregenerates the workspace file. Open that new file in XCode and voila, no more build errors.

Throughput answered 14/6, 2021 at 7:38 Comment(0)

C

0

We had the same issue, someone in our team had opened the Podfile.lock in Visual Studio Code, saved it, and the editor had removed the CR (carriage return) at the end of the file. Reintroducing the 'CR' solved the problem. So definitely run that command to figure out why those files are different.

diff "${PODS_ROOT}/../../Podfile.lock" "${PODS_ROOT}/Manifest.lock"

Consistency answered 21/4, 2022 at 18:19 Comment(0)

E

0

Remove Pods.framework in:

Folder named Pods Linked Frameworks and Libraries And delete all new inputed lines from @main file App for ios

Ebberta answered 5/8, 2022 at 12:43 Comment(0)

B

0

This helped me. Hope it helps you

remove

import 'dart:html'; unused

Bregma answered 29/11, 2022 at 17:57 Comment(0)

B

0

After lot of searching I found this solution:

pod install => you will get this error [!] No `Podfile' found in the project directory.
Use cd ios
pod install

In my case this worked for me:)

Bricker answered 27/12, 2023 at 12:25 Comment(0)

S

0

1.Open the terminal, type diff, and check the output.

diff [-aBbdilpTtw] [-c | -e | -f | -n | -q | -u] [--ignore-case]
        [--no-ignore-case] [--normal] [--strip-trailing-cr] [--tabsize]
        [-I pattern] [-F pattern] [-L label] file1 file2
diff [-aBbdilpTtw] [-I pattern] [-L label] [--ignore-case]
        [--no-ignore-case] [--normal] [--strip-trailing-cr] [--tabsize]
        [-F pattern] -C number file1 file2
diff [-aBbdiltw] [-I pattern] [--ignore-case] [--no-ignore-case]
        [--normal] [--strip-trailing-cr] [--tabsize] -D string file1 file2
diff [-aBbdilpTtw] [-I pattern] [-L label] [--ignore-case]
        [--no-ignore-case] [--normal] [--tabsize] [--strip-trailing-cr]
        [-F pattern] -U number file1 file2
diff [-aBbdilNPprsTtw] [-c | -e | -f | -n | -q | -u] [--ignore-case]
        [--no-ignore-case] [--normal] [--tabsize] [-I pattern] [-L label]
        [-F pattern] [-S name] [-X file] [-x pattern] dir1 dir2
diff [-aBbditwW] [--expand-tabs] [--ignore-all-blanks]
        [--ignore-blank-lines] [--ignore-case] [--minimal]
        [--no-ignore-file-name-case] [--strip-trailing-cr]
        [--suppress-common-lines] [--tabsize] [--text] [--width]
        -y | --side-by-side file1 file2
   diff [--help] [--version]

2.Create a new folder and copy Podfile.lock and Manifest.lock into it.

3.Run diff Podfile.lock Manifest.lock.

4.Type which diff.

5.Execute sudo rm /usr/local/bin/diff.

Socratic answered 1/2, 2024 at 7:39 Comment(0)

T

0

In case you ever hand-edited the Podfile.lock file, make sure there is a trailing newline at the end of the file (right after the "COCOAPODS: <version>" line).

I kept getting this error until adding the newline back in, which was a maddening experience.

Travax answered 27/3, 2024 at 16:8 Comment(0)

R

-1

You need to include Pods-generated xcconfig path in your customized xcconfig. For me this was due to that misconfigured xcconfig file.

Rotative answered 7/6, 2018 at 18:55 Comment(0)

I. Project Cleanup

II. Update CocoaPods

Recommended topics

Hot tags