Open stevekellyhpe opened 5 years ago
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 notifications@github.com<mailto:notifications@github.com> wrote:
@ortahttps://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 GitHubhttps://github.com/CocoaPods/CocoaPods/issues/8299#issuecomment-447109982, or mute the threadhttps://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 COCOAPODS_TRUNK_TOKEN
due to CocoaPods Trunk: Remote Code Execution found. Some sort of positive confirmation of a successful verification would be nice. CocoaPods/trunk.cocoapods.org#290 seems to be related.
I can also confirm that after clicking the link, even though it results in 404
, doing pod trunk me
in the terminal afterwards is successful.
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. eg: https://nam02.safelinks.protection.outlook.com/url=xyz
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.
[!] Source code for your Pod was not accessible to CocoaPods Trunk. Is it a private repo or behind a username/password on http?
static libs and podsec file are on git private repo and the command i use for publishing is
pod trunk push
Hi a have problem Technically it's a 404, but we're not too fussed I try to register my account. What to do I need to push SDK to the server Best regards JK Kontakt.io
Report
What did you do?
pod trunk register cloud@meridianapps.com 'Steve Kelly' --description='Steve Kellys 15 inch macbook'
What did you expect to happen?
I expected an verification email address to be sent to cloud@meridianapps.com. 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