Octokit.Net no longer working "bad credentials" or "AwaitingForActivation" #2846
Unanswered
Gregory-Lange
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a solution built for my job that will put Issue's into a GitHub repository from an internal app using Octokit.Net. I was just informed that sense mid December this automation was not working. I refreshed the token for the account that is doing the automation, as well as authorized it access to the Org. I just get bad credentials from the existing solution, which i updated to latest to be safe from 6.0.1 to 9.1.0 but still same issue. However when i created a clean solution and put in the correct data to send the new issue to the org i get "AwatingForActivation". This makes no sense as it was working before now so what has changed sense December with the authorization flows?
Beta Was this translation helpful? Give feedback.
All reactions