I can't fix problem with cocoapods. I'm trying to create private repo with some library. When I'm executing
pod repo lint MyLib --verbose
I'm getting error:
An unexpected version directory AppIcon.appiconset was encountered
for the MyLib/Images.xcassets Pod in the Images.xcassets
repository.
I dig google for solutions for it, but only hints was to update cocaPods. At this moment I've newest version but still no clue how to move forward.
Any ideas what to check?
You lost the extension.
pod repo lint MyLib.podspec
Related
I created a framework and wanted to distribute it via CocoaPods. For that I published the code to CocoaPod's Specs github repository (https://github.com/CocoaPods/Specs.git) using the command:
pod trunk push RXSStoryblokClient.podspec
The pod was successfully pushed to the trunk (https://github.com/CocoaPods/Specs/commit/b0a141b3c741d757090f61d1579ec92a7c0ebfb6) and on the outside everything seems to have worked. But when I create a small test project and try to install the newly created pod by adding it to the podfile and running
pod install
it tells me: Unable to find a specification for 'RXSStoryblokClient'
I have tried (as suggested by cocoapods) to update the repo using the
pod repo update
command, but this didn't resolve the issue.
Any help in this matter would be greatly appreciated!
The issue actually resolved itself. It seems CocoaPods had not finished some indexing work and 48h after pushing the pod spec to github, the installation finally worked.
I have successfully pushed my pod to CocoaPods two three days ago with version number 0.1.0. Yesterday I had to add some new features to the pod, so I have made changes in Xcode, Created multiple Swift files, modified existing code.
Then I know that, this version should go out as a new tag. So I have created a new tag 0.1.1. and pushed changes to remote repo in GitHub. Also changed tag in podspec file. GitHub master repo and 0.1.1 has the same code which is equal to the local code. And there are no warnings or errors in Xcode, everything was perfect.
Then I have to test my pod, I ran pod lib lint, which successfully passed validation. When I ran pod spec lint, it gave me multiple Xcode errors and warnings which I have solved hours ago.
As I could see that pod spec lint is not looking into current swift files or into newly modified code. It shown errors and warnings related old code, And podspec file has proper version and tag. Remote repo is up to date in master and also in 0.1.1.
What could be the possible solution for this? Why this is happening? My Xcode swift files have completely changed but pod spec lint is pointing to some old code, How?
Is it due CocoaPods cache problem ?
got the same problem, cocoapods cache is here:
cd /Users/<#ur user name#>/Library/Caches/CocoaPods/Pods
just delete /Pods directory and pod lint will work
or
pod cache clean YOUR_POD_NAME
Find the cocoapods working directory, remove it and then try to lint again:
$ find /private/var/folders -type d -name CocoaPods 2>/dev/null -exec rm -rf {} \;
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 have created a repo of my project in Github, i used AFNetworking cocoapod in my project. When i download my project from github and tried to run in xcode, it raises errors like 'undeclared identifier AFHTTPRequestOperation'
Could anyone please help me in resolving this issues.
It seems that you have not pushed your pod projects to the repo.
Go to you project/pod directory and run the command
pod install
For future remove pod from the .gitignore file if any.
If the problem still persist then edit you pod file and add
pod 'AFNetworking', '~> 2.5
then run the same command
pod install
I've created and submitted a podspec, BCJSONMapper, but when I search for it using pod search BCJSONMapper I receive the following error: [!] Unable to find a pod with name matching 'BCJSONMapper'.
The spec is in the master repo (it was submitted via trunk). I can use the pod as expected if I refer to a local copy of the podspec in a podfile (pod 'BCJSONMapper', :podspec => '~/path/to/local/copy/of/BCJSONMapper.podspec').
How do I fix this? This is the first podspec that I've submitted to the master repo so I may have missed something obvious.
I've fixed it. I solved it by removing my ~/.cocoapods/repos/master and letting Cocoapods re-initalize the repo. What was confusing was that the same error message was occurring on a different machine. It may have just been coincidence, but I guess it could also have been a bug in Cocoapods.