Code-settings-sync: ERROR: Sync : You cant edit GIST for user : XYZ

Created on 18 Apr 2017  路  12Comments  路  Source: shanalikhan/code-settings-sync

When trying tu upload my settings, most if the time it does not work and I get this error. When I take out the sync.gist ID, it works. My current gist has three revisions, but now I keep getting this error.

--

Visual Studio Code Version : [ 1.11.2]
Code Settings Sync Version : [ 2.6.2 ]
Operating System : [ WIN10]
Occurs On: [Upload ]
Proxy Enabled: [ No ]
GIst Id: [ ffbadf42996c9aac32d861ceaa9b820b]

bug 馃悰 fixed

All 12 comments

Same problem here. I installed the extension on Windows, synced my settings. Now I am trying to sync them on macOS to the same gist the Windows version created and getting this error. If I delete the sync.gist ID it creates a new gist and works (but my Windows version is not syncing with my macOS version).

@phifa , @igorkulman You have already provided the valid token to the extension, right ?
Also is there any exception logged in the developer console ?

Yes, the token is valid, otherwise it would not work with empty sync.gist ID and would not create a new gist.

@igorkulman

Also is there any exception logged in the developer console ?

Yes
screen shot 2017-04-18 at 17 44 03

solved?? I am also facing the same problem

I need to check from the console log, why its not matching the gist owner and your username.
In next version, when this error occur extension will display both username so we can further evaluate the problem.
Upcoming extension version will show the log.

I'm also getting this error. I was able to perform the initial upload from my home PC, then download it to my work PC. But when I use the >Sync > Update / Upload Settings I get the error about my user.

I am also experiencing this issue.

I am also experiencing this issue too,but I solved this after I use Sync: Advanced Options > Toggle Auto-Upload On Settings Change.

I have released v2.7.
Let me know if there is still problem.
Also please share your developer console image as i have added some logs, if problem occurs.

Ok, i havent heard any of you guys, so i think this issue is safe to close assuming its fixed.

Was this page helpful?
0 / 5 - 0 ratings