For some reason I now have 2 spec repos: /Users/kevin/.cocoapods/repos/master/Specs and /Users/kevin/.cocoapods/repos/master-1/Specs/. Whenever I pod install or push a new version to our private spec repo I get the error "Found multiple specifications", like this:
[!] Found multiple specifications for `AFNetworking (2.5.0)`:
- /Users/kevin/.cocoapods/repos/master/Specs/AFNetworking/2.5.0/AFNetworking.podspec.json
- /Users/kevin/.cocoapods/repos/master-1/Specs/AFNetworking/2.5.0/AFNetworking.podspec.json
[!] Found multiple specifications for `ObjectiveSugar (1.1.0)`:
- /Users/kevin/.cocoapods/repos/master/Specs/ObjectiveSugar/1.1.0/ObjectiveSugar.podspec.json
- /Users/kevin/.cocoapods/repos/master-1/Specs/ObjectiveSugar/1.1.0/ObjectiveSugar.podspec.json
(But a whole lot more then that, basically an error for every version of every pod used in the current project.)
This is the second time I have this problem. The last time I simply completely removed my .cocoapods folder and ran pod setup, but now I have this problem again. I'm using cocoapods 0.35.0.rc2. I think it happens when the shallow checkout is created.
Ah I see 0.35.0 is out now. Weird, I didn't get a notice from pod like I usually get. Anyway, I still have this problem, how would I best deal with this?
I would recommend just removing the master-1 repo, it was likely put there via a bug fixed in 0.35.
Alright, seems to be fine so far. I'll reopen if it happens again.
Damn, happening again:
$ pod update
Update all pods
Analyzing dependencies
Creating shallow clone of spec repo `master-1` from `[email protected]:CocoaPods/Specs.git`
And once that is done, I get the errors about multiple specifications again.
Any particular reason you're using the scp-style URLS instead of HTTPS?
Ehm I have no idea, I didn't do anything.. I've even completely removed my ~/.cocoapods folder and ran pod setup.
After running pod setup, the first time I run pod update it creates that shallow copy to master-1 once again.
What does your Podfile look like?
Ah!
source '[email protected]:CocoaPods/Specs.git'
source '[email protected]:gangverk/pods.git'
Pretty sure this is from the pre-trunk days where I had push access to the master spec repo. I've changed my podfile, problems seems solved. Thanks!
it helps, thanks a lot kevin !
I also encountered this problem, how to solve it?
how was this solved?
@kevinrenskers
Same for me:
`- /Users/user/.cocoapods/repos/cocoapods/Specs/d/d/6/ReachabilitySwift/5.0.0/ReachabilitySwift.podspec.json
how to solve this problem?
I think the newer issues are related to the switch to the CDN in 1.8.0
http://blog.cocoapods.org/CocoaPods-1.8.0-beta/
So the warning with master vs trunk like this:
[!] Found multiple specifications for `[...]`:
- /.cocoapods/repos/master/Specs/[...].podspec.json
- /.cocoapods/repos/trunk/Specs/[...].podspec.json
Fixed by running:
pod repo remove master
And changing in your Podfile:
- source 'https://github.com/CocoaPods/Specs.git'
+ source 'https://cdn.cocoapods.org/'
Most helpful comment
I think the newer issues are related to the switch to the CDN in 1.8.0
http://blog.cocoapods.org/CocoaPods-1.8.0-beta/
So the warning with
mastervstrunklike this:Fixed by running:
And changing in your Podfile: