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

Question

I ve encounter 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        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    gt  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    gt  0 20 0    - RestKit Search    gt  0 20 0    - RestKit Testing    gt  0 20 0   SPEC CHECKSUMS    AFNetworking  61fdd49e2ffe6380378df37b3b6e70630bb9dd66   RestKit  1f181c180105a92f11ec4f6cd7de37625e516d83   SOCKit  2f3bc4d07910de12dcc202815e07db68a3802581   TransitionKit  d0e3344aac92991395d4c2e72d9c5a8ceeb12910  COCOAPODS  0 29 0

User · Answer

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

User · Answer

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  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 the version of your team  In your project s root directory you only have Podfile and Podfile lock  Then you do pod install  CocoaPods just adds a safety check in place  to be sure you and all your other team members are using the same versions of everything   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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

Go to Build Phases -  Check Pods Manifest lock  Replace      PODS ROOT  Manifest lock   with     SRCROOT  Podfile lock     SRCROOT  Pods Manifest lock   Check in image

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

if your pods are empty    remove copy pods resources and check pods manifest  lock from build phases settings of your project

User · Answer

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

User · Answer

Run this  and your errors will vanish  rm -rf Pods  amp  amp  gem install cocoapods  amp  amp  pod install

User · Answer

After changing target name  My problem was xcconfig with old target names    Went to project file -  info -  configuration Removed old xcconfig  both Debug  amp  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

User · Answer

I had same error  First I update cocoapods using  sudo gem install cocoapods   then install pods using Pod install command worked for me

User · Answer

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  gt  Link Binary With Libraries  II  Clean build folder In XCode  Menu Bar   Product   Product - gt  Clean build Folder III  Update cocapods Run pod update

User · Answer

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

User · Answer

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

User · Answer

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   gt   dev null   to   diff    SRCROOT  Podfile lock     SRCROOT  Pods Manifest lock   gt   dev null   It helps me

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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- gt  Signing - gt  Team  the error was gone and the build succeeded

User · Answer

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  -

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

pod deintegrate  lt PROJECT gt  XCODEPROJ    will deintegrate cocoapods pod install    installs the pods

User · Answer

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

User · Answer

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   gt   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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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  amp  do pod install   3- Keep your rvm updated

User · Answer

If you remove all pods from your target in the Podfile  e g    target  myTarget  do pod  great-stuff      gt  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

User · Answer

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

User · Answer

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 Phrases   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

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

Examples related to cocoapods

Examples related to restkit-0.20