Token expired every time I make a new token

[cdeli]

Visual Studio Code Version : 1.12.1
Code Settings Sync Version : 2.7.0
Operating System : W10 1703
Occurs On: All upload and download
Proxy Enabled: No
GIst Id: 84b5596500caa4a7da3d05261aafdfbf81c9420b

Cannot use my GIST ID to sync at all. remade and regenerated 20+ times and every single time I am receiving this error

"Sync : Invalid / Expired Github Token. Please generate new token with scopes mentioned in readme. Exception Logged in Console." or just a general "Error" and nothing happens. I am using 2FA on my github account.

Am I missing a crucial step in this?

[beeblebrox3]

Event after reset settings, I can't update the token

[alexsasharegan]

Ditto here. Trying to figure out my sync for nightly and LTS build of VS Code.

[shanalikhan]

what are the developer console logs
Check this : #177 (comment)

[alexsasharegan]

Reseting Sync before issuing a new token was key for me. I guess it should go reset, gen token, then set new token. I tried to update token first, failed too many times, then got stuck in the 403 zone.

[shanalikhan]

In the next release, #310

You will be able to see the token also.

[alexsasharegan]

Well, you can see it in vscode settings under sync.gist. That was enough for me.

[shanalikhan]

@cdeli , @beeblebrox3
Did that help?

[cdeli]

No that did not work. Now I receive "Sync : Invalid / Expired Github Token. Please generate new token with scopes mentioned in readme. Exception Logged in Console." with no output log.

[shanalikhan]

with no output log.

Are you sure, developer console doesnt show any error ?
As it always write error on developer console.

[rkeithhill]

I'm seeing the same thing with expired GitHub token:

[rkeithhill]

I did get this to work by doing a settings reset. I think I was also confusing the previous GIST ID that settings sync doles out with the GitHub personal access token that GitHub doles out. I did have a settings.json conflict with the file on disk and what was loaded into VSCode. I'm pretty sure I picked the file on disk as that looked like it had all the right stuff that I had uploaded via my home PC.

Still, shouldn't have run into this because I did put in the GIST ID as it asked when I first tried to sync - which worked. It was when I tried to upload some tweaked settings from this same machine that I started to get token expired errors.

[aunsbjerg]

I am seeing this issue too. I installed the extension yesterday on my work computer (Win7) and had it working fine, could upload settings no problem. Then I installed the plugin on my home computer (ubuntu) and could download the settings, but got the invalid github token when trying to upload settings. I ended up creating a new gist and github token, but now I cannot sync settings from my work computer, even though I'm using the correct gist id and token.

It seems to me as if resetting the extension settings does not necessarily reset the github token. At least that is what I'm seeing now when I do the following:

• Reset extension settings
• Regenerate github token (with gist credentials checked)
• Attempt to download settings

So right now, the extension is not really working for me at all, which is a shame because it would otherwise be perfect.

[shanalikhan]

I have released new version.
Now you can place your token manually in extension local settings.
Please try again and let me know.

[Toizi]

Had the same issue. Regenerated a few times, reset settings and used upload but always failed.

To solve it I did the following

1. regenerate the token
2. reset settings + delete all the lines in settings.json with sync.*
3. restarted VS Code
4. upload settings