I recently started my first Xcode project (I am really new to app development) and I accidentally deleted a pod folder and moved it to the trash when I meant to simply delete the reference. I removed the Pod files from the left side bar out of the "Pods" folder and I was left with a pretty nasty set of errors.
The project no longer builds, I am no longer able to run "pod install" using terminal without getting errors, and I am worried that my project is completely trashed now after an immense amount of work I have put into the application and the pod created workspace. If you have any ideas on what to do, please offer all the help you can as I am terrified that I have corrupted the whole project.
Wanted to send an update for all of those who have a similar issue: I have resolved the issue and everything seems to be working again.
What I did to resolve the errors
I reinstalled Cocoapods using Terminal with the command $ sudo gem install cocoapods
Once it reinstalled, I ran the command pod cache clean --all (This removed all pod cache files)
Next, I ran the command pod deintegrate to remove all pod files
Once all pod files were removed, I ran the command pod install
After completing these steps, all the issues were resolved
I hope this helps someone else who may have similar issues due to improperly removing pod framework and module files or those who's
This article will help detail all the steps for installing Cocoapods for those who may be confused by my explanation to fixing these specific errors:
https://guides.cocoapods.org/using/getting-started.html
I'm trying to create a cocoa pod following this tutorial. I'm stuck at the moment where I'm doing the following command:
pod repo push RWPodSpecs RWPickFlavor.podspec
the problem is that I've got the following error:
Validating spec
[!] The `RWPickFlavor.podspec` specification does not validate.
And not further error description unfortunately. What I tried was reinstalling cocoapods and installing cocoapods keys, but it didn't help. I'm still getting the same error. Any ideas, guys?
I solved this issue by adding option --allow-warnings.
While the OP's issue was fixed, using this command will give more information about anyone else's issue. For me, I forgot to push the new version tag to my remote.
pod repo push [repo] [podspec] --verbose
Oh, the problem was very simple actually. I was simply being unobservant. In my .podspec file I had one of the urls formatted like that : ["https://github.com/Andrey-C/RWPickFlavor.git"]. Once I removed the square brackets around the url the error vanished.
Sometimes pod spec lint doesn't update changes (this is because of cache).
Once I fixed some errors specified by lint, pushed, updated tag, etc., and ... got the same errors as before.
So you can fix it by cleaning cache:
cd /Users/<#your-user-directory#>/Library/Caches/CocoaPods/Pods
just delete /Pods directory and pod spec lint will work again
For me, I needed to add a revision tag to my master branch and then git push with all tags before the pod trunk push would pass validation.
Use the following command:
pod trunk push RWPickFlavor.podspec
It publishes your newly created pod to CocoaPods repository, creating a pod with name that specified in your .podspec file.
You also have to use such command to publish a new version of your pod.
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:
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
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
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.
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
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.
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.
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
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)
I found my solution: Run:pod update instead of pod install. The error was fixed!
Go to Build Phases -> Check Pods Manifest.lock
Replace
${PODS_ROOT}/Manifest.lock
with:
${SRCROOT}/Podfile.lock" "${SRCROOT}/Pods/Manifest.lock
Check in image :
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.
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.
Try to set up the correct target in Podfile and then run pod update or pod install
Can you try this:
Delete the Pods folder
Delete Podfile.lock
Run pod install
Clean + Build
Run this, and your errors will vanish
rm -rf Pods && gem install cocoapods && pod install
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.
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.
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
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.
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"
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
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.
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.
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
Check Pods target and Runner target thats have to be same
1- Runner
2- Pods
Remove Pods.framework in:
Folder named Pods
Linked Frameworks and Libraries
And delete all new inputed lines from #main file App for ios
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.
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
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 :)
I had same error. First I update cocoapods using
sudo gem install cocoapods
then install pods using Pod install command worked for me.
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.