-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VS Code x86 - No Sign In and Share Button #102
Comments
The extension on first run should be downloading the dotnet-runtime and copying it to this dotnet_modules folder. Can you check if hostpolicy.dll is present anywhere under |
@LmKupke Could you run the following command and then drag-and-drop the resulting |
@srivatsn I checked the folder and didn't see any hostpolicy.dll in the folder and no zipped files as well. @lostintangent what directory should I be executing this command from the ms-vsliveshare? |
@LmKupke Oops, apologies for forgetting to ask that. Could you run that command from the |
@lostintangent I ran the command and got an empty files.txt file.
I executed the command from the /c/users/lkupke/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.146/dotnet_modules |
@LmKupke Ah OK, are you using Windows Subsystem for Linux? The previous command was for use with |
Ran the command here is the file I got |
files (1).txt |
I had the same problem on windows 10 as well (no problem on my mac). To fix it I :
|
@jrobber, the first install that had the issue- was that a fresh install or did you upgrade from an older version? |
Are you by any chance using a vs code workspace? i'm having the same issue too, but i don't seem to be getting the fatal error issue, only that the agent is terminating. It seems to be working for me though if I don't use a workspace. |
I'm getting the following error, and uninstalling and reinstalling as admin didn't help. I'm not using a workspace either. [Client I] Did not find user settings at C:\Users\user\.vs-liveshare-settings.json |
Hi there. If you are having the same trouble I did with VS live share preview the solution that worked for me is as follows:
This allowed me the sign in button at the bottom of VS Code |
I get the same error. |
@saraoneal did you follow the instructions above? In your case go to C:/Users/user/.vscode/exstensions/ And delete the folder ms-vsliveshare.vsliveshare |
Then try to add the extension again and reload vscode |
@saraoneal, can you please run the commands above to get the list of files in the extensions\ms.liveshare directory? The install step is opposed to unzip and move some files and I want to figure out which step failed. |
Yes, I followed the steps you suggested exactly. Here is the file generated from the command above. |
Thanks. Looks like the dotnet runtime did not get unzipped at all for some reason. Can you please find the log file under %temp%\vsfeedbackvsrtclogs? The most recently modified file would correspond to the latest session. That log file might tell us if it thinks it's unzipped the files or if something else went wrong |
Here's the latest log file. |
That log looks strange.. it says it's starting to install dependencies but no messages after that. One more request - could you please look to see if there's a file called install.lock in the extensions\ms.liveshare directory ( the command above listerd only directories). |
Yes, that file is there. |
I've the same problem, and prior to try the suggested workarounds I post here the files that maybe you'd like to have for investigation: Update:I've tried both suggested workarounds but without success. @LmKupke I think this issue should be reopened. |
OK, thanks to @srivatsn I've found that my instance of VS Code was indeed a 1.20.1 version but a x86 one, so I've uninstalled it and installed the x64 version, and now the plugin do works. These are the steps I've followed:
On restarting, I finally saw the This solved my issue, hope this can help. |
@ncarandini Eureka! I just tried reproing this and it happens 100% of the time using VS Code x86 on Windows. That appears to be the specific problem. @LmKupke Which architecture of VS Code are you using? x86 or x64? |
I can confirm that I am using the x86 version of VS Code. I can't upgrade at the moment, but will try soon. |
@saraoneal Thanks for confirming that! We're going to prepare a fix for x86 VS Code on Windows, since we can verify that is a source of at least some user's problems, but it would be awesome to confirm that you are unblocked once switching to x64 VS Code. |
@LmKupke Is it possible that you were using the x32/86 version of VS Code when you were hitting this bug, and you actually switched/upgraded to x64 when Live Share started working? When running the x32/86 version of VS Code, it will actually ask you if you'd like to upgrade to x64, so I just wanted to check if you happened to do that. |
@lostintangent this absolutely fixed my issue! Thank you all so much! |
@lostintangent Unfortunately I am unable to check now, because my work computer hard drive crashed. :( I lost all my applications and data. However once I am situated I can try again and see if I run into the same problems others are having |
@LmKupke @saraoneal @ncarandini We just published an updated VS Code extension that should resolve this issue (0.2.151). Apologies for the problem!! Let us know if you (or anyone else) running 32-bit VS Code are still seeing problems with this update. |
Another employee at our office upgraded his extension and he can now sign-in and attempt to share as well! Thank you all so much for the help. |
Great! Closing as fixed. We will re-open if anyone hits a problem here. |
FYI, If any one is still having this issue, check your user settings. I had a user setting to hide the status bar. Ooops! "workbench.statusBar.visible": true, is what you want. |
Product and Version [VS/VSCode]: VSCode
OS Version [macOS/Windows]: Windows 10
Live Share Extension Version: 0.2.146
Target Platform or Language [e.g. Node.js]: Node.js
Steps to Reproduce / Scenario:
I am unable to get the Sign In button on the bottom screen. Is there some dependency that I need for my computer?
The text was updated successfully, but these errors were encountered: