This is expected behavior since there is currently no tag which has been published and made available through CocoaPods.
I checked the current develop and it still works fine (TravisCI status is ok as well). The CocoaPods specification file also passes validation and is ready to be made available.
Let me know whether you are ready for a release so that we can proceed further. Publishing a 1.0 involves the following steps:
Bump version in version.xcconfig to 1.0
Release a 1.0 version using git-flow and push all changes to github
As described in the CocoaPods documentation linked above, the first user to push a version to the trunk becomes the project owner. The EBU should therefore perform the initial push. You can also add me as a contributor if you need me to be able to push versions in the future.
This is expected behavior since there is currently no tag which has been published and made available through CocoaPods.
I checked the current develop and it still works fine (TravisCI status is ok as well). The CocoaPods specification file also passes validation and is ready to be made available.
Let me know whether you are ready for a release so that we can proceed further. Publishing a 1.0 involves the following steps:
version.xcconfigto 1.0As described in the CocoaPods documentation linked above, the first user to push a version to the trunk becomes the project owner. The EBU should therefore perform the initial push. You can also add me as a contributor if you need me to be able to push versions in the future.
Thanks!