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
What happened instead is that I received an 500 "Internal Server Error" response.
Note that the initial form, that posts to "https://trunk.cocoapods.org/disputes/new" works without issue. It is the actual sending of the dispute that results in this error.
From looking at "disputes_controller.rb" I suspect there may be an issue with the Slack integration. However this is hard to say for sure without the actual server logs.
Could this issue please looked into? And could you perhaps clarify whether disputes are still received successfully, even though there is an error, or whether I need to make another dispute when the issue is resolved?
Thank you for your help!
The text was updated successfully, but these errors were encountered:
I've noticed this blog post.
Could you please indicate what this means for the dispute flow? Should we expect that the issues reported earlier will never be resolved?
Hi Trunk team!
I attempted to make a dispute/claim for a Pod by posting to "https://trunk.cocoapods.org/disputes".
As a result I expected to be redirected to "https://trunk.cocoapods.org/disputes/thanks".
What happened instead is that I received an 500 "Internal Server Error" response.
Note that the initial form, that posts to "https://trunk.cocoapods.org/disputes/new" works without issue. It is the actual sending of the dispute that results in this error.
From looking at "disputes_controller.rb" I suspect there may be an issue with the Slack integration. However this is hard to say for sure without the actual server logs.
Could this issue please looked into? And could you perhaps clarify whether disputes are still received successfully, even though there is an error, or whether I need to make another dispute when the issue is resolved?
Thank you for your help!
The text was updated successfully, but these errors were encountered: