Anthony Conrad (parithon)

I'm experiencing this behavior too. Version: 1.38.1 (system setup) Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0 Date: 2019-09-11T13:35:15.005Z Electron: 4.2.10 Chrome: 69.0.3497.128 Node.js: 10.11.0 V8: 6.9.427.31-electron.0 OS: Windows_NT x64 10.0.18362 ms-vsliveshare.vsliveshare: 1.0.950 vsls: 0.3.1291

Hi @lostintangent - unless I am doing something wrong whatever changed did not fix the issue for me. I am willing to do a live-share session to figure it out...

@lostintangent I still encounter this issue with my project.  

Yes, I do.

To test, I changed my extension id and publisher to match those used by **vscode-test-explorer-liveshare** and also changed the shared service name to match what is used in that extension...

I am the co-author of the following: https://github.com/clarkio/vscode-twitch-highlighter

> @parithon Hmm, that seems to indicate that our logic for the API permissions regressed, and is only allowing whitelisted extensions to call it. We should obviously fix that 😁...

I performed a live share test between my desktop and a VM with separate logins and the decorators did not sync between the two.

 Thank you for the enhancement request, I believe PR #93 will solve this issue.

I agree with this. A redesign of how settings are conveyed to the server is needed. Perhaps this can be accomplished during a major refactoring process prior to version 1.0?