-
Notifications
You must be signed in to change notification settings - Fork 253
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
[VSCode "OSS"] Extension activation fails: "Can't access Proposed APIs" #262
Comments
For Solus Linux, this was located at /usr/share/vscode/resources/app/product.json See #215 for this and other issues related to Solus. EDIT: This particular issue is resolved for Solus with the latest vscode package. libcurl should also be resolved soon. |
Are you running the latest insiders build, just released? |
@grork It worked for me yesterday on Windows 10 with
Stopped to work after update today:
I can see that this problem is reproducible on 2 PCs. Both have correct values in
|
Update, there has been a regression in the latest version of VS Code Insiders which has caused a regression in how they manage proposed APIs. Unfrotunately this has caused issues for us and resulted in the errors you mentioned above. Fortunately, the VS Code team is rolling out a fix to insiders which rectifies this regression and it should be generally available tomorrow. |
@avanderhoorn I'm on the latest official insiders build for Windows x64, but the "Proposed API" issue still exists. My full version info:
|
This issue is has been closed due lack of any recent activity. We've made lots of improvements to Live Share since this issue. Please re-open the issue, if this issue persists. |
I know that this is a closed issue. but here is a Python Script for the lazy to fix that: #!/usr/bin/env python
import os
import json
VSCodeProductPath = "/usr/lib/code/product.json"
if not os.path.exists(VSCodeProductPath) or not os.access(VSCodeProductPath, os.W_OK):
print("ERROR: Insuficient permissions or did not find VSCode Product file:", VSCodeProductPath)
exit(1)
VSCodeProduct = open(VSCodeProductPath, "r")
data = json.load(VSCodeProduct)
# We need to ensure the extensionAllowedProposedApi has the following array:
extensionsToAdd = [
"ms-vsliveshare.vsliveshare",
"ms-vscode.node-debug",
"ms-vscode.node-debug2"
]
print("Before:", data["extensionAllowedProposedApi"])
for extension in extensionsToAdd:
if extension not in data["extensionAllowedProposedApi"]:
data["extensionAllowedProposedApi"].append(extension)
print("After:", data["extensionAllowedProposedApi"])
print("Rewriting to file:", VSCodeProductPath)
VSCodeProduct = open(VSCodeProductPath, "w")
json.dump(data, VSCodeProduct, indent=4) You file location might changes, this works on Arch Linux, since everytime the package is updated you need to re-fix the |
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/microsoftdocs/live-share (branch main)
Non-offical distributions of Visual Studio Code can be missing a critical value in
product.json
file that prevents Visual Studio Live Share from activating. In this case, if you go to Help > "Toggle Developer Tools", you will see stack traces indicating the Live Share extension did not activate due to it using a "proposed API."To verify this is your issue, check the contents of
product.json
. The file can be located as follows:C:\Program Files\Microsoft VS Code\resources\app\product.json
/usr/share/code/resources/app/product.json
/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/product.json
If the
extensionAllowedProposedApi
property is missing or you do not see "ms-vsliveshare.vsliveshare" referenced, you are using an unofficial version with this problem. Contact the VS Code distribution owner to get the issue patched.As a workaround, you can add the following into the product.json:
The text was updated successfully, but these errors were encountered: