New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty podfile makes my project not build #3617
Comments
I know this has come up before, but we really should make this work. |
You can use https://github.com/kylef/cocoapods-deintegrate to deintegrate your project from CocoaPods. Related to and possibly duplicates #2471. |
Option: We could treat it as a "do you want to remove CocoaPods" and offer how to install cocoapods-deintegrate? |
This situation is actually a case where you don't want to remove CocoaPods but just don't have pods that you want to use at the moment. One workaround similar to the one I'm using may be: when the Podfile is empty, under the hood pretend that it includes one (mostly empty) package of code and builds that in. |
Consider this a +1. When setting up a project (particularly for a distributed team) where you know you're going to use pods, but don't have any specific ones picked out yet, this is a real pain. It'd be nice for it to gracefully work without requiring you to add a pod. |
This also applies for the case when you add a pod (say RxSwift) to the main target and other pods (say Quick, Nimble) to the testing target. If I remove the sole main target pod (RxSwift) but still want to keep my testing target pods installed, (say because I switch to ReactiveCocoa and they advise to add manually, not with cocoapods), the main project will no longer build (missing breaths out edit: a work around to that is to run |
This is surely known already but it didn't show up on a search. I removed the last pod from my Podfile, did pod install and then my project wouldn't build anymore.
I don't want to remove cocoapods wholly since I think I will be using it again in the near future but it can happen that your need for pods is at zero. Shouldn't it still work then?
I fixed my problem by adding a generic library as a pod after which my project does build again.
The text was updated successfully, but these errors were encountered: