The TapkuLibrary podspec on the CocoaPods repository only includes 0.2.3, so 0.2.4 isn't visible to anyone who doesn't manually download the podspec from your repo. If you've not done this before, this guide explains how to update the spec they have to be the newest. The gist is that you just need to fork their specs repo, copy the new podspec to it in a 0.2.4 subfolder, push it, then submit a pull request to them.
The current podspec in your repo doesn't pass validation (so wouldn't be accepted as is):
- WARN | The summary should end with proper punctuation.
But to fix that, it's literally enough just to put a period at the end of the summary.
As a side effect of doing this, the "Homepage" link on Cocoapods.org for this library would point to the correct page, whereas right now it points to tapku.com (which I don't think is you).
The TapkuLibrary podspec on the CocoaPods repository only includes 0.2.3, so 0.2.4 isn't visible to anyone who doesn't manually download the podspec from your repo. If you've not done this before, this guide explains how to update the spec they have to be the newest. The gist is that you just need to fork their specs repo, copy the new podspec to it in a 0.2.4 subfolder, push it, then submit a pull request to them.
The current podspec in your repo doesn't pass validation (so wouldn't be accepted as is):
- WARN | The summary should end with proper punctuation.
But to fix that, it's literally enough just to put a period at the end of the summary.
As a side effect of doing this, the "Homepage" link on Cocoapods.org for this library would point to the correct page, whereas right now it points to tapku.com (which I don't think is you).
Thanks again for creating this library.