-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Connections to marketplace #418
Comments
Open VSX marketplace is available in v1.46.0 and higher. |
That looks like an open vsx bug to me. Can you open an issue at https://github.com/eclipse/openvsx/issues and link it to this one? |
I will reopen this in case anyone else is having the same issue connecting to open vsx. |
cc @spoenemann |
I'm facing this same issue. VSCodium details - Version: 1.46.0 |
Hi all, I'm also impacted by this issue. codium build: Version: 1.46.0 |
I tried to delete config files for a full reset and the problem still persists. |
FYI since this was a comment on #415, the docs have a method to revert back to the VS Code Marketplace. I have done this temporarily until the issue (eclipse/openvsx/issues/126) is addressed. |
Hi, i'm having the same issue: Versión: 1.46.0 (user setup) |
@GammaGames any idea where to place product.json on my filesystem for MacOS? I ran sudo find / -name product.json and it came back with nothing. EDIT: Just found it:
|
Same problem:
|
Quick workaround: Edit Replace:
with:
|
@phd I don't have such folder... I installed VSCodium with AppImage 🤔 |
Thank you so much @phd! It's working now! |
@phd Life saver! |
Why did we switch to open-vsx then? To go back to Microsoft's marketplace? |
Also we have no access to open-vsx because of Iran sanctions but Microsoft's marketplace is working |
@Rowisi Good question, but probably because the licensing restrictions to Microsoft's marketplace needs more investigation. I'm wondering if we could add a feature to VSCode to be able to choose the Marketplace from the UI. I think that would be handy. |
Same issue using VSCodium Temporary workaround: File: |
I upgraded to 1.46 and the market place stopped working. The console is showing 500 errors:
I was using brew to manage VSCodium however I cannot select the previous version (1.45) so I manually reverted using the binary provided here and the market place started working again. |
it works now |
i really think that this is a bad move. But this lead me to throw VSCodium away and install VSCode. Open-VSX may be a nice place, but for me it caused some problems! I now fix this but it was even not easy to find this thread here when searching for this issue... |
I understand that this marketplace switch presents a regression since there aren't nearly as many extensions available from Open VSX as there are from MS. Much appreciation to anyone submitting ad-hoc solutions for using the MS marketplace -- I encourage the people in this thread who have come up with methods to submit PRs to the README/DOCS so that others who want to use Microsoft's marketplace can possibly have that option without digging through issues. VSCodium will be sticking with Open VSX for the foreseeable future. I said from the beginning (on the README since almost first commit) that VSCodium would use Microsoft's extension marketplace until there was an open source alternative. Ideally MS would allow extension marketplace to be configured in the app's settings instead of baked-in at build time. I'm not sure if this is on their roadmap (but doubtful since they will want everyone using their proprietary marketplace). Closing this issue for now (although feel free to comment if I've missed something still pending in this issue). I will create a readme banner or issue template so that it's easier for anyone unaware of this change to figure out what happened in recent versions. |
By default vscodium uses open-vsx.com for extension library (IUSE="ext_vsx"). To revert to Microsoft markplace, use the 'ext_msm' use flag. See VSCodium/vscodium#418 for more information.
Is there any way to make in permanent? After every update I have to
Is there any way to make it permanent? I mean after every update I have to manually change it back to MS store. |
Not atm, at least that I'm aware of. Honestly MS should just make marketplace a setting instead of a "compile-time" var. |
OR
|
Or command to fix it
|
BTW if you use the flatpak that switch that is also documented in the Readme is a little more complicated. See flathub/com.vscodium.codium#22 for a solution in the Flathub version. |
My new work-around is using |
is there an alternative to vscodium? i dont want the gates snooping, but I need plugins that are only on the microsoft store. |
VSCodium/vscodium#418 (comment) -> VSCodium/vscodium#674 Signed-off-by: Kipras Melnikovas <[email protected]>
On a packaged Mac app, replace the content with |
clearing cache from product.js file with code from @phd is the solution. Just find product.js file where you installed VS Code |
awesome ! Thank you. 💟💟💟💟💟 |
After an hour of troubleshooting on what I did wrong in my parrot OS, finally I got the actual error and found this post. I cannot thank you enough! :) |
For me, this file was not there. Instead I tried that here |
Had the same issue once, i was able to solve it by modifying hope it works for you too credit: to @xip-niekneuij at |
Describe the bug
I went to Network and I saw that vscodium is connecting to
https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery
Reading Docs page I learned about product.json which is said to be set to open-vsx.org. I checked /usr/share/codium/resources/app/product.json and I found that
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"itemUrl": "https://marketplace.visualstudio.com/items"
},
It does not seem that way.
Please confirm that this problem is VSCodium-specific
I do not use vscode, so i do not know.
Please confirm that the issue/resolution isn't already documented
To Reproduce
Steps to reproduce the behavior:
Browsing or installing extensions.
Expected behavior
No connections to Microsoft MarketPlace.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: