Sanders Lauture
Sanders Lauture
Can you paste your CodeSync logs here? They are available in the Output view (View > Output > CodeSync)
Yes if extensions.json is being created that means the CLI path was found. Once you manually set the VSCode settings path for CodeSync whenever you try and export settings this...
What OS are you on? I tried this in Linux and I am not getting this error.
This is a VSCode error, the problem with nailing down where this error is, is that VSCode can't output the stacktrace of extensions.
If you're able to setup the extension locally you should be able to get a stack trace while debugging. That would be very helpful.
What version of VSCode are you using? The extension basically leverages `code --install-extension` on the command line to install extensions. This was introduced in [1.2.0](https://code.visualstudio.com/updates/May_2016). If `code --install-extension` doesn't work...
I've noticed with Code 1.6 that I haven't been experiencing this issue at all. Can anybody else confirm?
I've been pretty busy with finishing up college and moving but hopefully I should be able to take a good look at this within the next month or two.
Still haven't been able to figure out why this is happening but version 2.3.0 makes it so that you will be able to use all the features except for importing...
I have added logging to version 2.4.0 to help with debugging this issue. If you are still experiencing this issue please paste your log here. The CodeSync log is located...