I added an external framework via cocoapods into my iOS application. How can i remove that library from the project?
7 Answers
Remove lib from Podfile, then pod install again.
- 12,690
- 11
- 64
- 119
- 17,178
- 11
- 66
- 105
-
11When I do this, I'm left with dozens of warnings in XCode 5 complaining that the workspace can't find the removed files. I've tried to manually clean this up but have not been successful. How can you cleanly remove a pod? – Matt Mombrea Dec 19 '13 at 01:18
-
8Find the pods file in Finder, then delete each of the individual pods (you'll notice they're missing the .h and .m files). Then `pod update`. That worked for me. – AMayes Jan 09 '14 at 22:32
-
1Also remember if library A is referenced by library B, which is also in Podfile, library A won't be removed even if you remove its entry and run "pod install". Library A will only be removed if you also removed the entry for library B. – CodeBrew Mar 06 '15 at 05:20
-
9You also get the warnings that @MattMombrea mentions if you successfully deleted the podfiles, but haven't committed the change. Make sure everything is committed to the code repository. – HughHughTeotl Oct 02 '15 at 11:10
-
1The article that @vrunoa mentions is now a dead link. This article is helpful: http://stackoverflow.com/questions/16427421/how-to-remove-cocoapods-from-a-project – Lane Rettig Jan 14 '16 at 19:51
-
2I want to delete a framework installed by pod without updating or installing podfile – Anand Prakash Nov 18 '16 at 11:03
The unwanted side effects of simple folder delete or installing over existing installation have been removed by a script written by Kyle Fuller - deintegrate and here is the proper workflow:
Install clean:
sudo gem install cocoapods-cleanRun deintegrate in the folder of the project:
pod deintegrateClean(this tool is no longer available):pod cleanModify your podfile (delete the lines with the pods you don't want to use anymore) and run:
pod install
Done.
- 3,358
- 2
- 22
- 34
- 15,101
- 9
- 71
- 103
-
2This pod should be the accepted answer, because it is much more thorough. Although, before following this workflow, I would suggest to clear the contents of the project's Derived Data directory, and make sure to commit the project's changes to the existing code repository. Finally, after running `pod install`, I opened the Xcode xcworkspace file, performed a full clean on the build folder (alt+shift+command+K), and the warnings/linker errors were gone. Pods were now successfully uninstalled from the project. – Mark Barrasso Jan 30 '17 at 21:30
-
Note to @All: This command`cocoapods-clean` deletes the `Podfile` and `.xcworkspace` – Suhaib Jun 15 '17 at 11:02
-
8Seems now `pod deintegrate` is official: http://guides.cocoapods.org/terminal/commands.html#pod_deintegrate No need for `sudo gem install cocoapods-deintegrate`. – Pang Aug 07 '17 at 04:54
-
I found that when I removed SwiftLint from my project, that I also had to manually remove a line referencing it from the run script. – Vince O'Sullivan Apr 05 '18 at 07:55
-
5I second that from @ZinWinHtet, when I try `pod clean` I get: `$ pod clean [!] Unknown command: clean` – ScottyBlades Sep 21 '18 at 22:12
-
3
-
-
I had a project where I incorrectly added a podfile. I then changed it by changing teh text and restarting teh project which is incorrect. Then I tried this and it did not work at that point – Feb 26 '19 at 21:30
-
Fully completing all these steps did the trick. I still had to remove a few Pods-related files from the Finder and Xcode, but the Xcode project file built correctly after replacement of the pods with Swift Package Manager. – Womble Feb 10 '20 at 03:03
Remove the library from your Podfile
Run
pod installon the terminal
- 7,710
- 5
- 32
- 51
- 275
- 3
- 3
None of these worked for me. I have pod version 1.5.3 and the correct method was to remove the pods that were not longer needed from the Podfile and then run:
pod update
This updates your Podfile.lock file from your Podfile, removes libraries that have been removed and updates all of your libraries.
- 87
- 1
- 3
-
3You don't need to update all the libraries in your project (something that can be very dangerous) just to remove a library. There are much better ways in this thread including removing the pod from your podfile and then running `pod install` – Braden Holt May 26 '20 at 20:20
-
1This updates all versions of your libraries and naturally removes the one that is not present anymore in the Podfile, but do you really want to update the libraries ? Removing the pod and `pod install` is the correct way. – Karim Mortabit Jun 02 '20 at 23:25
- Remove pod name(which to remove) from Podfile and then
- Open Terminal, set project folder path
- Run pod install --no-integrate
- 516
- 3
- 14
First, determine which versions of Cocoapods are installed :
gem list --local | grep cocoapods
You get output as this:
cocoapods (1.11.2)
cocoapods-clean (0.0.1)
cocoapods-core (1.11.2, 1.10.2, 1.10.1)
cocoapods-deintegrate (1.0.4)
To completely remove, issue the following commands:
gem uninstall cocoapods
gem uninstall cocoapods-clean
gem uninstall cocoapods-core
gem uninstall cocoapods-deintegrate
Running again to confirm that Cocoapods has been removed:
gem list --local | grep cocoapods
You may have residual artefacts in a hidden folder in your directory. Remove these with:
rm -rf ~/.cocoapods
- 21
- 2
Remove pod name from Podfile then
Open Terminal, set project folder path and
Run pod update command.
NOTE: pod update will update all the libraries to the latest version and will also remove those libraries whose name have been removed from podfile.
- 938
- 1
- 13
- 24