I was so excited to get a private repo at CocoaPods. I got v1.0 from my small internal library working with my main application, like a charm. Then I added something to the library, made it, tagged it v1.1, pushed it, and everything went straight to hell.
No matter what I do, although my main application reports that my internal library is pointed to 1.1, I keep getting the same code as 1.0. I'm at a dead end.
Things I checked:
- My private repo container has the correct folder structure, and the files
.podspecin each folder have correspondings.version - Did the file match the two files
podspecon my internal pods repository and confirm that the only change to the file was the version number. - I helped
git checkout tags/1.1in the repo with the internal library and confirmed that the tag 1.1contains the corresponding commit. - The file confirmed using the BitBucket website is changed and the tag for
1.1made it there.
I also tried the following steps to solve it (which I can remember now) and still got the same code added to the Pod.
- Removing a damaging module from a subfile, starting
pod updateto delete it, re-adding it and re-executing it pod update. - Cleaning
~/Library/Caches/CocoaPodsand [ProjectRoot]/Podsand starting up pod install. pod repo remove [NAME], .- : head
- podspec , .
- podspec .
- git Xcode, CocoaPods , , , , , pod update ,
- ? .
1/24: :
pod install
Analyzing dependencies
Downloading dependencies
Installing [Private Library] (1.0)
Installing Google-Mobile-Ads-SDK (6.7.0)
Installing LARSAdController (3.0.3)
Installing UIAlertView-Blocks (0.0.1)
Generating Pods project
Integrating client project
[!] From now on use `[App Name].xcworkspace`.
, , 1.0, - . , :
pod update
Analyzing dependencies
Downloading dependencies
Installing [Private Library] (1.1)
Using Google-Mobile-Ads-SDK (6.7.0)
Using LARSAdController (3.0.3)
Using UIAlertView-Blocks (0.0.1)
Generating Pods project
Integrating client project
, . , , , , , , , 1.0? ?