-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trunk register verification email leads to 404 #123
Comments
Still seeing the same issue. |
Tried again this morning, still getting a 404. |
@orta any insights here? I don't have any visibility into trunk to know what's happening |
So I just realized this morning that the registration was actually successful, and I was able to post a new version of our SDK. The 404 is confusing in that regard, but not as high priority as I assumed. Thanks for looking into it though.
…-Steve
On Dec 14, 2018, at 7:29 AM, Eric Amorde <[email protected]<mailto:[email protected]>> wrote:
@orta<https://github.com/orta> any insights here? I don't have any visibility into trunk to know what's happening
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/CocoaPods/CocoaPods/issues/8299#issuecomment-447109982>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZ-mRY0hMx20UrNWbOH4RRC6t-fMpSxPks5u4ri5gaJpZM4YqAiB>.
|
I think we delete the verification code from db post verification, so we can't really say "token expired" if it succeeds and you try do it again without adding more data to the db, so it's likely that this will not get fixed. |
Hi @orta I've performed the exact same steps as @stevekellyhpe described and got the same result with the following display from verifying the link in the email: Going off what was said in this thread, can you confirm that the registration was successful? |
I'm seeing the same issue. |
Same for me |
Same for me now |
I'm also seeing this now having to create a new I can also confirm that after clicking the link, even though it results in |
I am also facing the same issue. I get a session verification link to my outlook enterprise from cocoa pods in which it is somehow damaged. Any quick fixes? |
Your verification is accepted, just not by you, so your CLI will be working just fine - we just don't persist that verification token after the first check |
I get this error when trying to publish the static libaries. static libs and podsec file are on git private repo and the command i use for publishing is |
Hi a have problem Technically it's a 404, but we're not too fussed |
Report
What did you do?
pod trunk register [email protected] 'Steve Kelly' --description='Steve Kellys 15 inch macbook'
What did you expect to happen?
I expected an verification email address to be sent to [email protected]. When I clicked on the link in that email I expected the verification process to be complete.
What happened instead?
The link in the verification email sent me to a 404. I then attempted the same command line registration as before thinking maybe I hadn't been fast enough. And again was directed to a 404 page. One of the links was:
https://trunk.cocoapods.org/sessions/verify/8838de81
CocoaPods Environment
Stack
Installation Source
Plugins
Project that demonstrates the issue
Our Cocoapod is:
https://cocoapods.org/pods/MeridianSDK
The text was updated successfully, but these errors were encountered: