$ pod install
Updating local specs repositories
Analyzing dependencies
[!] Unable to find the Xcode project
`~/Desktop/TestAfnetwork.xcodeproj` for the target `Pods`.
When i run install command then i got this issue.Please solve my problem. I have already updated this setup.
Firstly, you should cd to your path /Users/vallesoft/Desktop/TestAfnetwork by using Terminal.
Secondly, type pod init to create Pod file
Finally, make sure that your Pod file look like this
target 'TestAfnetwork' do
pod 'AFNetworking', '~> 2.6'
end
Good luck
Related
I use pod 'LinqToObjectiveC' to install this specific cocoapod but i get back [!] Unknown command: LinqToObjectiveC
Did you mean: deintegrate?
There are no specific instructions at https://cocoapods.org/pods/LinqToObjectiveC
I do not know if i can install it using the pod command or not.
Any help to install it via pod command?
You need to add the following lines to your Podfile:
pod 'LinqToObjectiveC', '~> 2.1'
more info: https://cocoapods.org/pods/LinqToObjectiveC
I am trying to install 2 pod files without affecting/updating other dependencies in my pod file.
I tried with pod install --no-repo-update command. It is not working.
I want to install Fabric pod file when I try to install other dependencies are also updating and I don't want it because some dependencies are deprecated and it will show some warning and error, this is I don't want so I am trying to install pod without affecting and updating other pod files.
Here is the screenshot, in xcode I am getting 197 warnings. Before the installation of pod file there were 6 Xcode warnings.
pod 'Fabric'
pod 'Crashlytics'
You cannot install specific pod but you update specific pod.
Reference
https://guides.cocoapods.org/using/pod-install-vs-update.html
Pod install
Use pod install to install new pods in your project. Even if you already have a Podfile and ran pod install before; so even if you are just adding/removing pods to a project already using CocoaPods.
Pod Update
Use pod update [PODNAME] only when you want to update pods to a newer versio
To install new pod without updating others, just open up the existing file and add your pod file below the existing pods.
Now, go to terminal and open up your project and run command:
$ pod install
Note: This way, it will only add new pod without updating your existing pods.
When pod install , get this warning .How to solve the question? Please help me.Thank U very much.
[[!]Your Podfile requires that the plugin cocoapods-no-dev-schemes
be installed. Please install it and try installation again.]
If you have shown your podfile it will more helpful still you can try
sudo gem install cocoapods-no-dev-schemes and after it installs successfully you can try installing the pods again
Or
You can make the podfile structure to default structure in which you don't need any additional plugin like this:
platform :ios, '8.0'
use_frameworks!
target 'MyApp' do
pod 'AFNetworking', '~> 2.6'
pod 'ORStackView', '~> 3.0'
pod 'SwiftyJSON', '~> 2.3'
end
I tried below steps from terminal
$ sudo gem install cocoapods-repo-update
Then fire
$ pod install
This should work now.
Background :
cocoapods-repo-update is a CocoaPods plugin that checks your dependencies when you run pod install and updates the local specs repositories if needed.
As of CocoaPods 1.0, pod install does not update the master specs repo every time it is run. This is because CocoaPods was hammering Github with this behavior. Now the specs repo must be explicitly updated with pod repo update or pod install --repo-update.
This plugin checks if your CocoaPods specs repo needs to be updated when pod install is run and updates it if needed. This eliminates the need to run pod repo update or pod install --repo-update when you change a pod.
Source: https://github.com/wordpress-mobile/cocoapods-repo-update
I installed CocoaPods by using $ sudo gem install cocoapods.
I have a swift Xcode project with the following podfile
platform :ios, '8.2'
use_frameworks!
target 'Clover' do
pod 'Alamofire', '~> 1.2'
pod 'SwiftyJSON', '~> 2.2'
pod 'ObjectMapper', '~> 0.12'
pod 'ImageLoader', '~> 0.3.0'
pod 'SVProgressHUD'
end
target 'CloverTests' do
end
After I run pod install, which seems to run correct with no error messages, I have a Pods folder generated with Pods.xcodeproject along with several other files.
However, when attempting to compile the project, I will into errors telling me my modules are not found. The error message is No such module followed by the module name.
I then attempted to install the modules manually and confirmed that the pods are indeed not working as each module after its manual installation, works.
I have searched and attempted several solutions as follows:
Deleted and reinstall pod.
Upgraded ruby to 2.2.1
Delete the pods folder and re-run $ pods install.
Clean the project.
More a comment than an answer, but I don't have enough reputation to comment:
When you use pod install with your-project.xcodeproject, it creates a new file/folder named your-project.xcodeworkspace (…project becomes …workspace) and this is this new file that you should open.
You didn't mention whether or not you knew that, so here you go: close the .xcodeproject in Xcode and open the .xcodeworkspace instead and it should work.
I already have one project working with a podfile.
I wanted to add a Podfile on an old project but I got this error on
sudo pod install
Error:
Resolving dependencies of `./Podfile'
Updating spec repositories
[!] git pull
Updating 35bbbaf..8b42708
error: The following untracked working tree files would be overwritten by merge:
AFXAuthClient/1.0.4/AFXAuthClient.podspec
Please move or remove them before you can merge.
Aborting
It's weird because I don't use AFXAuthClient on my project, and I never used it.
Here's my Podfile:
platform :ios, '5.0'
pod 'TTTAttributedLabel', '~> 1.6.0'
pod 'ECSlidingViewController', '~> 0.9.0'
I tried to made without success:
gem install cocoapods
pod setup
NB: I get the same error with pod setup
From the command line run rm -rf ~/.cocoapods
Then run pod install again. You shouldn't need the sudo.
This look like it's caused because there was a change to a spec and it's conflicting with running a git pull
If you're seeing an error like this, it might be because CocoaPods had to force-push their repo. They suggest:
pod repo remove master
pod setup