-
Notifications
You must be signed in to change notification settings - Fork 4
0.2.6 -> 0.2.7 - Bad Credentials #6
Comments
Hi @aki77, Thanks for your reply, here's my settings, with a new token in. REally not sure why all of a sudden it's stopped working I uninstalled the package and re-installed (it maintained my token), but still getting Bad Credentials error. I'm feeling like it's actually causing an internal error with the package, because once the error occurs, the package won't work unless I open another tab to use it on; |
Please test your token using the curl.
Replace "OAUTH-TOKEN" with your actual token. |
Yeah that works fine. |
No such file or directory. I have resolved the issue however. I thought it was odd that it was returning the double token. So I deleted the token and tried again.. watch.. The value of the token field is literally;
So somehow I managed to paste in the token twice, with a new line between them. And for some reason the single line options allow new line characters (which you then can't see). My bad, but potentially needs some extra validation on that field so that it doesn't contain new lines, or maybe it's a bug with Atom. Happy for this to be closed, unless you want to keep it open and add some validation? |
Noted with thanks! 😃 |
Added debug settings. |
👍 nice one, thanks! |
Hello,
Since updating to 0.2.7 today, I just get the 'Bad Credentials' error when I try and list my Gists. I can't see anything in the changes that would have affected this.
I have tried generating a new token and working with that, but get the same error.
Is there some more debug info I can get that would be useful?
The text was updated successfully, but these errors were encountered: