You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just created a pod for our project : https://seald.io, called SealdSdk
The problem is, our developer mistakenly published his first test as v1.0.0.
I then successfully deleted the version in question with the pod trunk delete command.
However, it is still this 1.0.0 version, which does not exist anymore, which shows on the cocoapods.org search. So, clicking on the podspec does not work, and updates to it (the description for example) are not taken into account.
At first, I thought that it was because I had only published beta versions after this, so I tried publishing a semver-stable version, and it still appears to be the case.
Hello !
We just created a pod for our project : https://seald.io, called
SealdSdk
The problem is, our developer mistakenly published his first test as v1.0.0.
I then successfully deleted the version in question with the
pod trunk delete
command.However, it is still this 1.0.0 version, which does not exist anymore, which shows on the cocoapods.org search. So, clicking on the podspec does not work, and updates to it (the description for example) are not taken into account.
At first, I thought that it was because I had only published beta versions after this, so I tried publishing a semver-stable version, and it still appears to be the case.
The Specs repo however seems to be updated correctly: https://github.com/CocoaPods/Specs/tree/master/Specs/2/8/2/SealdSdk .
I don't know how I can trigger a forced synchronization for cocoapods.org . Is there something like that?
Thank you !
The text was updated successfully, but these errors were encountered: