CocoaPods Errors on Project Build

Question

I m unable to build a project that uses CocoaPods  I get the following 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       pod install seems to work fine and adds a Pods Project to my Workspace  I ve tried   pod update but this doesn t help   It seems that PODS ROOT is not being set   Podfile   platform  ios   6 0   workspace  Example xcworkspace  xcodeproj  example Example xcodeproj    pod  TestFlightSDK      gt  1 3 0-beta 5  pod  TestFlightLogger      gt  0 0 2  pod  CocoaLumberjack      gt  1 6 2  pod  Reachability      gt  3 1 0  pod  SBJson      gt  3 2  pod  MKMapViewZoom      gt  1 0 0

User · Answer

In my case  this was a test target that I removed all the pods from inside my podfile  because I added pods that I later realized I did not need in that target   None of the other solutions here worked for me    Go to the Build Phases tab in the project settings for the target that s causing trouble  Delete the section named  Check Pods Manifest  and  Copy Pods Resources  Inside  Link Binary With Libraries  remove libPods-YourTarget a In your project settings in the Info tab expand  Configurations  and set the configuration for the target to None for both debug and release   This will fix a couple of missing file warnings  Delete your project s derived data  Window   Projects   Delete  next to your project  and restart Xcode  Build   run target

User · Answer

I think it has a bug here  For me  I delete Pods folder and Podfile lock and do the pod install again to solve the problem  This message is ignoring

User · Answer

This issue got it solved    Select Target of your Project Select Build Settings Open User-Defined drop-down list Change value of key PODS ROOT to   SRCROOT  Pods

User · Answer

In my case I did put Podfile lock  amp  Manifest lock in source control  but I forgot to add Pods-Project debug release  xcconfig files to source control  by mistakenly adding   xcconfig to  gitignore   then I got the same compile errors with exactly the same reason  PODS ROOT is not being set   So if the goal is that after cloning the repo  the project can immediately build and run  without having CocoaPods installed on the machine  you either add entire Pods directory in source control or add Podfile lock  Manifest lock  project s xcconfig files and Pods xcconfig files to source control   I didn t put the private  xcconfig that merges the build settings with the default CocoaPods configuration to source control

User · Answer

Had the same issue saying   Pods Pods-resources sh  No such file or directory even after files etc related to pods were removed   Got rid of it by going to target- Build phases and then removing the build phase  Copy Pod Resources

User · Answer

If you have a watchOS target  I found that suddenly  having pods in the watch extension but not in the watch target itself broke things with this same error  The solution was to add the pods to the watch target also

User · Answer

In my case the problem was in the wrong way  solution here http   guides cocoapods org using troubleshooting html     If something doesn   t seem to work  first of all ensure that you are   not completely overriding any options set from the Pods xcconfig file   in your project   s build settings  To add values to options from your   project   s build settings  prepend the value list with   inherited

User · Answer

I got rid of the same problem by doing following steps    Xcode- gt Product- gt Clean Build Folder  hold alt key on Product to see it  Open Xcode- gt Window- gt Organizer and select Projects tab  Then find your project and delete derived data of the project

User · Answer

if you added new target after creating Podfile  just delete Podfile  Podfile lock   Pods folder and workspace  then  init pods - then put your pods pod install

User · Answer

I had same problem with the my IONIC project  i tried above all solutions but not luck     If you have same problem still  check weather below settings are present in Build Settings  - gt   User-Defined settings or not   1 PODS ROOT  2 PODS PODFILE DIR PATH    If not present then add it   PODS ROOT     SRCROOT  Pods  PODS PODFILE DIR PATH     SRCROOT     It will solve problem  solution link

User · Answer

TLDR  This is most likely a bug with Xcode and closing and reopening the project is usually the simplest fix  Assuming everything else is configured properly     I occasionally get the same error when deleting the Pods directory and then running pod install   Everything appears correct in the project info     However  when I go to the target s User-Defined Build Settings  the PODS ROOT entry is either entirely missing or is empty for one or more configurations  Which causes the following error on build     The simplest fix is to close the project in Xcode and reopen it   If you go to the target s Build Settings and filter on All  you will now see the PODS ROOT entry with no errors     It should now build with no errors      Note  Even Cocoa Pods  official AFNetworking iOS Example has this problem  which leads me to believe that it is a bug with Xcode   An alternative fix is to manually change the configuration to None  then back to its original value

User · Answer

After spending hours i found the solution go to  Build Phases   Then  Check Pods Manifest lock   Tick  Run Script only when installing   Thank me later

User · Answer

In my case  I accidentally typed an unnecessary dot at the end of the config file which caused this strange problem  Please make sure your config file does not contain any errors

User · Answer

I had this issue    The way I fixed it was by completely deleting the Pod implementing and re-implementing it  Make sure to delete  Copy Pods Resources  and  Check Pods Manifest lock  from  Build Phases  on all targets as stated here  How to remove CocoaPods from a project

User · Answer

Go to the target s Build Settings and make sure the value of PODS ROOT equals   SRCROOT  Pods in  User-Defined  section

User · Answer

gem install xcodeproj   may help you   See pod install fails with abort - New Swift project

User · Answer

So it seems that CocoaPods didn t set the Configurations for my Project  They need to be based on the Pods xcconfig which is found in the Pods Target Support Files Pods  To get this to work I had to do the following    Drag this file into my Xcode Project in Xcode  choosing not to copy  Now there is a reference in our project  we can set the configurations     I then had another build error which may or may not have been related  The path to the shell script defined in the Copy Pods Resources was incorrect       SRCROOT  Pods Pods-resources sh    Resolved incorrectly  It seemed that SRCROOT was adding an extra dir that didn t exist into the path  So I hard coded the path to the Project folder   This allowed me to build   Why is it that so many things that are supposed to save you time end up eating it up   Note  Please see  abood s answer for explanation

User · Answer

update  a podfile lock is necessary and should not be ignored by version control  it keeps track of the versions of libraries installed at a certain pod install   It s similar to gemfile lock and composer lock for rails and php dependency management  respectively   To learn more please read the docs  Credit goes to cbowns     In my case  what I did was that I was doing some house cleaning for my project  ie branching out the integration tests as a git submodule   removing duplicate files etc    and pushed the final result to a git remote repo   all the clients who cloned my repo suffered from the above error  Inspired by Hlung s comment above  I realized that there were some dangling pod scripts that were attempting to run against some non-existent files  So I went to my target build phase  and deleted all the remaining phases that had anything to do with cocoa pods  and Hlung s comment he suggests deleting Copy Pods Manifest lock and copy pod resources   mine were named different maybe b c I m using Xcode 5   the point being is to delete those dangling build phases

User · Answer

I have a similar issue this is what worked    In Xcode    Clean Delete Derived Data in Xcode Window Organizer Project Your Project Pod directory  it contains config files  delete files not just references   Removed all references to the pod config files for every target in Project Configurations  debug release  Removed  Targets Build Phases Copy Pods Resources  from all Targets Removed  Targets Build Settings User-Defined PODS ROOT  from all Targets  Quit Xcode In your project directory    rm -rf Pods  Optional  rm -rf YourProject xcworkspace rm -rf Podfile lock  pod install Open YourProject xcworkspace in Xcode

User · Answer

I had a similar problem when I did major changes to my Podfile  My solution was to remove the workspace file and run pod install again   rm -rf MyProject xcworkspace pod install

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

It wasn t very intuitive  I went to the base project settings and then I hardcoded paths to my pod lock and pod manifest under Check Pods Manifest lock  because they stayed in different folders in fact  so my paths looked like this   diff   Users admin Desktop Experimental projectfolder Podfile lock    Users admin Desktop Experimental projectfolder Pods Manifest lock   gt   dev null if          0      then     cat  lt  lt  EOM error  The sandbox is not in sync with the Podfile lock  Run  pod install  or update your CocoaPods installation  EOM     exit 1 fi

User · Answer

open  xcodeproj file in sublime text remove these two lines  if you have clean pods folders  i mean if you got the errors above after you removed pods folder

User · Answer

I had the same problem recently  I have tried every possible advice  nothing except this plugin has worked for me   https   github com kylef cocoapods-deintegrate  After the cleaning up of the current cocoapods integration  what s left to be deleted are Podfile  Podfile lock and the  xcworkspace  Then just install all over again   I hope I will help someone with this

User · Answer

You can try the following  It fixed for me    install gem install cocoapods-deintegrate install gem install cocoapods-clean goto   pod deintegrate pod clean pod install   The plugins will be remove from cocoapods for your project and will install freshly

User · Answer

I had the same issue  After retracing my recent steps  I found that adding a target declaration for a new target  followed by running pod install  was the cause of the problem     Resetting my branch and cleaning my project did not work  since Cocoapods modified at least one file that is not under source control  I know this because once I reset the remote branch to a commit before adding the extra target  and re-cloned the repo  the problem no longer existed

User · Answer

For me to get rid of this error  I needed to delete the Pods directory and delete the Podfile lock file

User · Answer

After trying the above  I realized I was getting an error on pod install         CocoaPods did not set the base configuration of your project   because your project already has a custom config set    This was causing the error  because cocoapods was not adding the  xcconfig file to my project   To solve this I went to the Info tab of my project   Set my Based on Configuration File to None for all schemes and targets   Then re-ran pod install  See this link for more information  Cocoapods Warning - CocoaPods did not set the base configuration of your project because because your project already has a custom config set

User · Answer

I have created multiple targets before I ever used pods  Later when I started to compile the other targets I had to add link with with the list of targets in my Podfile

User · Answer

Simply resolved by doing the following     sudo  gem install cocoapods pod install clean and build   it seems the problem was caused by one of our team members having a more recent cocoapods gem installation

[objective-c] CocoaPods Errors on Project Build

Examples related to objective-c

Examples related to cocoa-touch

Examples related to cocoapods

Examples related to build-error