We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's more difficult to complete my work
When attempting to edit an API Key, an error (500 Internal Server Error) is encountered at POST https://www.nuget.org/account/EditCredential.
500 Internal Server Error
POST https://www.nuget.org/account/EditCredential
The end user receives a generic error alert on the website:
Upon inspecting the failed request via DevTools, I could see the HTML directing me to file an issue:
Error was encountered when editing an API Key owned directly by my account, as well as keys belonging to an org to which I am an owner/administrator.
Current Workaround:
https://www.nuget.org/account/apikeys
API Key settings are saved.
Provided in description.
No response
The text was updated successfully, but these errors were encountered:
Sorry about this, meantime you can unblock yourself by deleting the existing key and recreating it.
Sorry, something went wrong.
No branches or pull requests
Impact
It's more difficult to complete my work
Describe the bug
When attempting to edit an API Key, an error (
500 Internal Server Error
) is encountered atPOST https://www.nuget.org/account/EditCredential
.The end user receives a generic error alert on the website:
Upon inspecting the failed request via DevTools, I could see the HTML directing me to file an issue:
Error was encountered when editing an API Key owned directly by my account, as well as keys belonging to an org to which I am an owner/administrator.
Current Workaround:
Repro Steps
https://www.nuget.org/account/apikeys
Expected Behavior
API Key settings are saved.
Screenshots
Provided in description.
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered: