Skip to content
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

Closed
alper opened this issue May 28, 2015 · 6 comments
Closed

Empty podfile makes my project not build #3617

alper opened this issue May 28, 2015 · 6 comments
Labels
t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future.
Milestone

Comments

@alper
Copy link

alper commented May 28, 2015

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.

@segiddins
Copy link
Member

I know this has come up before, but we really should make this work.

@kylef
Copy link
Contributor

kylef commented May 29, 2015

You can use https://github.com/kylef/cocoapods-deintegrate to deintegrate your project from CocoaPods.

Related to and possibly duplicates #2471.

@orta
Copy link
Member

orta commented May 29, 2015

Option: We could treat it as a "do you want to remove CocoaPods" and offer how to install cocoapods-deintegrate?

@alper
Copy link
Author

alper commented May 30, 2015

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.

@neonichu neonichu added the t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future. label Jun 3, 2015
@dbburgess
Copy link

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.

@iandundas
Copy link

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 Target Support Files/Pods-MainTargetName), but cocoapods-deintegrate won't help here either, as we're still using cocoapods for testing.

breaths out

edit: a work around to that is to run pod deintegrate, delete the project's workspace, then pod install will generate a fixed workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future.
Projects
None yet
Development

No branches or pull requests

7 participants