Pod ref is missing for version 0.1

[Vkt0r]

With the pull request I made before I fix the issue with the SwiftSafe.podspec, but if necessary to make the pod trunk push SwiftSafe.podspec with the respective credentials for the owner of project to be SwiftSafe available again in the Specs of Cocopoads with the correct version.

Right now is impossible to build Buildasaur because it depends of BuildaUtils that depends on SwiftSafe.

It would be great 😅 integrate the library in the Specs to continue the contribution on Buildasaur.

[dominik-hadl]

As I mentioned in the PR I am just waiting for the ownership of the pod to get transferred to me and then I will update the trunk. 🎉

[Vkt0r]

Yep @nickskull I closed it. Thanks

[tomhut]

Hey @nickskull , did you ever get ownership in the end? (Also running into this issue!)

Thanks!

[dominik-hadl]

@tomhut Hey, I did! As far as I remember I have also pushed to trunk.

What exactly is your issue? :)

[tomhut]

@nickskull Good to hear! I'm looking to build XcodeServerSDK, which has a dependency on BuildaUtils v0.3.2 which depends on SwiftSafe 0.1 via CocoaPods. When trying to do so however the following error is generated by CocoaPods.

warning: Could not find remote branch v0.1 to clone. fatal: Remote branch v0.1 not found in upstream origin

Any help greatly appreciated!

Update

Perhaps this could be the issue, the repo url for 0.1 seems to be pointing to an old location? And I can't seem to see the tag on the current repo. https://github.com/CocoaPods/Specs/blob/d0ec5a65e80656c8d78e12ff19f251df879e0bc2/Specs/b/2/8/SwiftSafe/0.1/SwiftSafe.podspec.json

[dominik-hadl]

@tomhut Reopened this.

You are right, there seems to be issues with tags/branches and outdated podspec. As far as I remember Github redirects to new repo url if you rename/transfer it.

But either way the branch/tag does not exist anymore, so I'll investigate what's necessary to fix this.

[tomhut]

@nickskull Interesting, thanks so much!

[dominik-hadl]

@tomhut I can't seem to figure out what's the best way of fixing it, since I don't use CocoaPods as often.

Either I can re-add the wrong tag on the same commit as the 1.0.0 version, or I'd have to make a patch version to cocoapods and buildautils would have to be updated.

What do you think could be a way of solving this? Should I try and add the commit that the the spec at version 0.1 specifies ("v0.1")?

[E-B-Smith]

@nickskull I think you can simply tag the correct commit, like this:

git tag 0.1 77ffd12b02678790bec1ef56a2d14ec5036f1fd6
git push
git push --tags origin master

If it doesn't work you can delete the tag.

The tag should show up here: https://github.com/nodes-ios/SwiftSafe/releases

[dominik-hadl]

@E-B-Smith I did now, let me know if it fixed the issue :)

[E-B-Smith]

Still not good. Did you publish the podspec too? On the revision, try something like:

pod trunk push Branch.podspec

You may need to set the version in the podspec too.