[VS Code] Object reference not set to an instance of an object.

[rajatdeshpande]

[Chuxel]

@rajatdeshpande Thanks for reporting this issue. However, we could use a bit more details to help you out.

1. What OS and OS version are you running?
2. When did you encounter this error?
3. It would be useful to see your logs. Can you run the Live Share: Export Logs command and either drag-and-drop the zip into a comment or email them to vsls-feedback@microsoft.com

[ewoudje]

I have the same problem on visual studio, i am running windows 10 i did encounter this error when trying to join a session... logs: https://pastebin.com/VTT2MDMm

[Priya91]

[VSIX E] System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.VisualStudio.LanguageServices.Remote.Guest.RoslynLSPClientServiceFactory.CreateServiceAsync(SessionContext sessionContext, CancellationToken cancellationToken)
   at Microsoft.Cascade.Client.Extensibility.CollaborationServiceProvider.<CreateServicesAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Cascade.VsSessionConfigurator.<ConfigureSessionForJoiningAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runt...

cc @srivatsn @daytonellwanger

[srivatsn]

@rajatdeshpande @ewoudje Do you by any chance have the Language Server Client Preview extension installed? We've found that we run into this error if that extension is installed.

/cc @rodrigovaras

[ewoudje]

Yes i have that installed... is there already an issue open for it?

[srivatsn]

I've filed #410 to track the extension conflict issue. This issue was originally filed for VS Code and so that is a different issue from #410

[Chuxel]

@rajatdeshpande We've had several updates to fix a number of issues in this space. Can you confirm whether or not you are still seeing this error in VS Code?

[lostintangent]

Closing due to inactivity.