Unable to find a specification in CocoaPods

Question

I cannot understand why the Cocoapod is unable to find the pod specification I created when I run pod install. Could someone help me solve this trouble?

I'm defining a subspec in my library podspec file like this:

s.subspec 'mysubspec' do |c|
  c.dependency 'ABC','1.0.0'
end

This dependency ABC is listed in the library Podfile:

pod 'ABC', :git => 'git@github.com:myrepo/Podspecs.git', :branch => 'xyz'

The Podspec file ABC.podspec in the branch xyz of myrepo/Podspecs seems like this:

Pod::Spec.new do |s|
  s.name         = "ABC"
  s.version      = "1.0.0"
  s.source       = { :git => "git@github.com:myrepo/Podspecs.git", :branch => "xyz" }
end

The error is [!] Unable to find a specification for ABC (= 1.0.0)

score 189 · Answer 1 · edited Mar 13 '18 at 14:36

189

I suppose that there is a problem with your pod master repo. Delete it and download it again.

You can do:

pod repo remove master
pod setup
pod install

Or:

sudo rm -fr ~/.cocoapods/repos/master
pod setup
pod install

edited Mar 13 '18 at 14:36

chancyWu

14,073
11
62
81

answered Sep 29 '15 at 17:55

Gastón Antonio Montes

2,559
2
12
15

52

Just running `pod setup` did the job. – Nagendra Rao Jun 02 '16 at 13:10
1

For me, only running the remove line first solved the problem! Took a while to setup though. – sinewave440hz Jul 22 '16 at 12:04
2

Wow! This. For some reason my Spec master repo wasn't setup correctly and I had to remove it this way and then did the setup and install. Thanks for this! – praneetloke Jan 12 '17 at 20:22
1

'pod setup' took quite a while, but was all I needed (as Rao mentioned) – Chris Allinson Feb 01 '17 at 23:23
1

Tried multiple other solutions, this is the one that did it for me (first solution) – Jake T. Apr 04 '18 at 17:55
6

Might want to try `pod repo update && pod setup` first - if your repo is just missing specs this might fix it and will be faster than re-cloning the whole repo from scratch. – Eliot May 16 '18 at 15:23
1

This is working, for the first time only. After restart / pod install in another project... fail fail fail again. use tis method instead. https://stackoverflow.com/questions/45287082/using-private-pod-and-public-pod-in-the-same-project/50618926#50618926 – zuyao88 Aug 23 '19 at 04:18
2

It may be called `trunk` rather than `master`, in case you get 'repo master does not exist' – Chris Watts Jul 30 '21 at 09:18

score 43 · Answer 2 · answered Dec 11 '14 at 19:50

43

For me it was an issue with finding the spec, not the spec itself. I needed to add a source link to the Podfile, see Podfile documentation

Cocoapods recently added the need to link to the repo that holds the pod spec file you are looking for, the default is:

source 'https://github.com/CocoaPods/Specs.git'

You may need to add multiple source links if you are using more obscure or homemade pods.

answered Dec 11 '14 at 19:50

dloomb

1,952
22
26

1

This can't be a requirement (at least not with the latest release), because I have not needed to added source links and after following Gastón's suggestion all worked fine. – sinewave440hz Jul 22 '16 at 12:08
@sinewave440hz, adding the source is most often used when you need to access a nonstandard private `.git` repo. The default source is public. – ScottyBlades Sep 10 '18 at 17:43
I see, thanks (not that I remember writing any of that, but I'm sure it will help someone somewhere :D) – sinewave440hz Sep 10 '18 at 17:53

score 26 · Accepted Answer · answered Sep 18 '14 at 13:21

26

Instead of:

s.source       = { :git => "git@github.com:myrepo/Podspecs.git", :branch => "xyz" }

Write this: Don't forget the tag...

s.source       = { :git => "https://github.com/myrepo/Podspecs.git", :branch => "xyz",
                   :tag => s.version.to_s }

answered Sep 18 '14 at 13:21

gran33

12,421
9
48
76

U have to tell the pod which tag r u talking. It's a must. – gran33 Sep 18 '14 at 13:42
Simply, add tag to your last commit – gran33 Sep 18 '14 at 13:43
1

I'll try it. Unfortunately, it's not in the Podspec documentation. – Gaius Augustus Sep 18 '14 at 14:24
It did not solve the problem: `[!] Unable to find a specification for `ABC (= 1.0.0)` – Gaius Augustus Sep 18 '14 at 17:09
Can u please add to your question your podspec file? – gran33 Sep 19 '14 at 13:05
1

I solved the problem! I have to import the pod ABC before importing the subspec. – Gaius Augustus Sep 19 '14 at 17:32
`:tag` is *not* required – Wayne Sep 29 '15 at 17:57

score 12 · Answer 4 · answered Dec 19 '16 at 17:04

12

Make sure you added

source 'https://github.com/CocoaPods/Specs.git'

at the very beginning of your Podfile

answered Dec 19 '16 at 17:04

Ugo Marinelli

989
1
11
18

3

This is especially relevant if you want to add a private pod. – Stan Feb 06 '19 at 02:14

score 7 · Answer 5 · answered Mar 06 '17 at 06:45

7

I resolve this after add

source '/Users/username/Documents/path/to/iOS_SpecsRepository'
source 'https://github.com/CocoaPods/Specs.git'

to Podfile. well .I used a local repository as my Repo. So i can user this in another podspec file

s.dependency 'iOS_Networking_CPN', '~> 0.1.1'

iOS_Networking_CPN is in the local path.

answered Mar 06 '17 at 06:45

OmniBug

892
8
12

source '/Users/username/Documents/path/to/iOS_SpecsRepository' worked, do you know why I have to use a local source path? – gabbler Aug 30 '18 at 04:14
in my opinion,because every device need a local repository for a podspec – OmniBug Aug 31 '18 at 01:29

score 7 · Answer 6 · answered May 29 '17 at 12:04

7

With me, this worked like a charm.

pod repo remove master
pod setup

However, you may try directly, pod setup as some users pointed.

answered May 29 '17 at 12:04

Hemang

26,840
19
119
186

zeeawan · Answer 7 · 2016-06-13T18:29:07.763

5

I was getting similar error for MGBoxkit

[!] Unable to find a specification for MGBoxkit

By replacing the following line

pod 'MGBoxkit'

with

pod 'MGBoxKit'

fixed the issue.

edited Jun 13 '16 at 18:29

answered Jun 13 '16 at 17:58

zeeawan

6,667
2
50
56

what is the difference? – Gargo Jul 27 '16 at 19:46
Typo as k was replaced with K. – zeeawan Jul 28 '16 at 10:33

score 4 · Answer 8 · edited Jan 17 '21 at 05:49

4

Update the master repo for cocoapods.

pod repo update master

edited Jan 17 '21 at 05:49

aturan23

4,798
4
28
52

answered Jan 23 '17 at 21:33

Idan Magled

2,186
1
23
33

score 3 · Answer 9 · answered Apr 24 '19 at 17:11

3

You first need to add your Podspec to a private specs repo; this lets CocoaPods find the pod when you try to install it.

Enter the following in Terminal, making sure you’re still in the framework directory you are trying to add:

pod repo add [your framework name] [Your framework Git URL]
pod repo push [your framework name] [your framework .podspec file name]

answered Apr 24 '19 at 17:11

Jevon Charles

644
1
7
12

Doesnt feel true when the pod is hosted on `trunk` – David Seek Apr 29 '21 at 00:34

score 1 · Answer 10 · answered Jan 09 '18 at 11:15

1

I missed adding , causing issue.

Replacing,

pod 'PodName' '~> 2.3'

With,

pod 'PodName', '~> 2.3'

Did the job.

answered Jan 09 '18 at 11:15

Mohammad Zaid Pathan

16,304
7
99
130

score 1 · Answer 11 · answered Jan 18 '18 at 12:19

1

I solved my problem with below command:

cocoa pod update

To update use this command

sudo gem install cocoapods

if above command gives error than use this one

sudo gem install -n /usr/local/bin cocoapods

and than do this

pod repo update

answered Jan 18 '18 at 12:19

Seema Sharma

379
3
12

score 1 · Answer 12 · answered Sep 06 '20 at 19:29

I was working in flutter with all public repos. I was getting a similar error:

Unable to find a specification for `TOCropViewController (~> 2.5.2)` depended upon by `image_cropper`

For some reason TOCropViewController specification was unavailable. I tried the following:

flutter clean
rm -Rf ios/Pods
rm -Rf ios/.symlinks
rm -Rf ios/Flutter/Flutter.framework
rm -Rf ios/Flutter/Flutter.podspec
rm ios/Podfile
flutter run

But the plugin specification was still unavailable. Finally, I solved it by removing the pod's repo master.

pod repo remove master
sudo rm -rf ~/.cocoapods/repos
pod setup
pod install

To validate and confirm that the plugin is here, I tried grep inside .cocoapods, using:

 grep -r "TOCropViewController" -n ~/.cocoapods

Inside ~/.cocoapods/repos/trunk/Specs/3/7/4/TOCropViewController/2.5.2/TOCropViewController.podspec.json

I found the plugin's git repo and correct version number.

  "source": {
    "git": "https://github.com/TimOliver/TOCropViewController.git",
    "tag": "2.5.2"
  },

After that flutter clean and flutter run started working.

score 1 · Answer 13 · answered Sep 10 '22 at 13:45

1

I had to add these two lines at the beginning of the Podfile:

source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/goinstant/pods-specs-public'

Then run pod install again.

answered Sep 10 '22 at 13:45

Abel Rodríguez

474
5
6

score 0 · Answer 14 · answered Mar 22 '18 at 02:01

had the same problem.

what really worked for me was gem uninstall cocoapods (as mentioned above by https://stackoverflow.com/users/4264880/seema-sharma) where I found that I had 11 (!) different cocoapods versions installed.

I chose to uninstall all and then gem install cocoapods:1.4.0

All good now.

score 0 · Answer 15 · answered Apr 30 '18 at 20:34

0

For me, the below worked well but first try could be direct "pod setup" command If that don't work then go for the below commands would definitely make things happen.

pod repo remove master
pod setup
pod install

answered Apr 30 '18 at 20:34

Sathish

416
1
6
20

How does this differ from @gastón-antonio-montes's [answer](https://stackoverflow.com/a/32850706/1998086)? – Leo Mar 29 '19 at 14:19

score 0 · Answer 16 · answered May 02 '19 at 06:34

0

Follow the below steps :

Step 0: pod repo update master

Step 1: pod install

And you are done!

answered May 02 '19 at 06:34

Sunil Targe

7,251
5
49
80

score 0 · Answer 17 · answered Aug 23 '19 at 04:19

0

use tis instead. Using private pod and public pod in the same project

add the souce for both private and public(official) in the beginning of the podfile.

answered Aug 23 '19 at 04:19

zuyao88

64
8

score 0 · Answer 18 · answered Apr 06 '20 at 15:14

None of the answers helped me. Ultimately i figured out that I had a typo spelling mistake for one of the Pods.

Ex:- Firebaseresulrereres/Analytics. It was supposed to be Firebase/Analytics but without my knowledge the pod name had a wrong spelling like Firebaseresulrereres/Analytics.

Correcting the Pod Name did the trick for me!. It cost me 1 hour to find this though!. Development can be ambiguous and frustrating some times! :)

score 0 · Answer 19 · answered Jul 22 '21 at 09:08

0

pod update

Solved the same error in my case.

answered Jul 22 '21 at 09:08

Nuzhdin Vladimir

1,714
18
36

Unable to find a specification in CocoaPods

19 Answers19

Linked