Code-settings-sync: Unable to now configure the extension with the command palette

Created on 14 Jun 2018  ·  9Comments  ·  Source: shanalikhan/code-settings-sync

Describe the bug
A clear and concise description of what the bug is.

Visual Studio Code Version : 1.24.1 (Insiders 1.25.0)
Code Settings Sync Version : 2.9.2
Operating System : Windows any
Occurs On: Download/Upload
Proxy Enabled: [ No ]
Gist Id: [ multiple ]

Just install VS Code and then add the Sync extension. I reload and then want to only configure it to download settings from my Gist. I use the command palette to select the download and all it does is open a browser window to GitHub profile.

There is now no open to actually configure anything with the extension using the command palette.

You can do the same steps around the upload option, all it does is open a new browser window. VS Code does not leave the command palette open when it looses focus (switch to another app).

question ❓

Most helpful comment

On osx you can go manually to /Users/youruser/Library/Application Support/Code/User and create a file named syncLocalSettings.json with the following structure:

{"ignoreUploadFiles":["projects.json","projects_cache_vscode.json","projects_cache_git.json","projects_cache_svn.json","gpm_projects.json","gpm-recentItems.json"],"ignoreUploadFolders":["workspaceStorage"],"replaceCodeSettings":{},"gistDescription":"Visual Studio Code Settings Sync Gist","version":292,"token":"your gh token","downloadPublicGist":false,"supportedFileExtensions":["json","code-snippets"]}

All 9 comments

The image that is shown in the readme of this repository is no longer what you receive in VS Code now.

image

This is what I receive, and had to do a screen record and pause to just be able to read it completely....as soon as you hit enter I get a browser window and this message is not actually readable:
image

It also does not appear to honor having the gist configuration manually added to my settings.json folder. Even after reload I try to download and it still wants me to try and create a token....so how are we to get it setup now?

On osx you can go manually to /Users/youruser/Library/Application Support/Code/User and create a file named syncLocalSettings.json with the following structure:

{"ignoreUploadFiles":["projects.json","projects_cache_vscode.json","projects_cache_git.json","projects_cache_svn.json","gpm_projects.json","gpm-recentItems.json"],"ignoreUploadFolders":["workspaceStorage"],"replaceCodeSettings":{},"gistDescription":"Visual Studio Code Settings Sync Gist","version":292,"token":"your gh token","downloadPublicGist":false,"supportedFileExtensions":["json","code-snippets"]}

@fernandofleury thanks. that hack worked for me

So for Windows do the following:

  1. Open PowerShell prompt
  2. Run:
    VS Code: New-Item "$env:USERPROFILE\AppData\Roaming\Code\User\syncLocalSettings.json"
    Insiders: New-Item "$env:USERPROFILE\AppData\Roaming\Code - Insiders\User\syncLocalSettings.json"
  3. Open file in Notepad:
    VS Code: notepad "$env:USERPROFILE\AppData\Roaming\Code\User\syncLocalSettings.json"
    Insiders: notepad "$env:USERPROFILE\AppData\Roaming\Code - Insiders\User\syncLocalSettings.json"
  4. Paste contents below:
{"ignoreUploadFiles":["projects.json","projects_cache_vscode.json","projects_cache_git.json","projects_cache_svn.json","gpm_projects.json","gpm-recentItems.json"],"ignoreUploadFolders":["workspaceStorage"],"replaceCodeSettings":{},"gistDescription":"Visual Studio Code Settings Sync Gist","version":292,"token":"your gh token","downloadPublicGist":false,"supportedFileExtensions":["json","code-snippets"]}

```

Actually I just tried the above process on Insiders and it does not work, but I no longer get a browser popping open either so it might be fixed on latest release of the extension.

@wsmelton I did the manual file creation for insiders on OSX and it worked for me. Maybe something went wrong for you in the process?

Guys!
This is a bug in Visual Studio Code Insiders
and is fixed by the team
https://github.com/Microsoft/vscode/issues/52361#event-1689780415

@shanalikhan you are totally right. at least we are providing some fallback while it isn't fixed

Was this page helpful?
0 / 5 - 0 ratings