[Bug] [Can fix] Not working on VSC 1.70 update

[rainbowflesh]

Run any command like Enable Vibrancy will have this

Something went wrong: Error: ENOENT: no such file or directory, stat 'c:\Users\myname\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-browser\workbench\workbench.html'

I keep the workbench folder to VSC 1.70, but still not working at all.

---

Edit: Follow @nbbaataraa's guide, or see the pr https://github.com/EYHN/vscode-vibrancy/pull/147, modify vibrancy extension/index.js will fix this bug.

[nbbaataraa]

i have same issue. then i go to vscode extension's dir. and find eyhn.vscode-vibrancy-1.0.16/extension/index.js. And replace electron-browser to electron-sandbox. then go to c:\Users\myname\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-sandbox Dir. Copy all files and past to c:\Users\myname\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-browser. then reload and re enable vibrancy. it works...

[dogdogduck]

I tried your method and it didn't work

[Rup-Royofficial]

Facing this error despite uninstalling and installing, Tweaked a couple of paths for the location of the said folder, yet it isn't working

[rainbowflesh]

Facing this error despite uninstalling and installing, Tweaked a couple of paths for the location of the said folder, yet it isn't working

Follow @nbbaataraa's guide, checkout pr #147, simply modify vibrancy extension/index.js will help.

[Rey-Wang]

@nbbaataraa @rainbowflesh MacOS 12.4 the instructions could clear the error, but transparent is gone.. not work anymore

[nbbaataraa]

works fine for me. And Windows OS too.

[MayconAlexsander]

When will the changes (last commit) take effect? I've already reinstalled Vibrancy and it still doesn't work...

[Rey-Wang]

even delete all vscode folders and reinstall vscode, still not work...

[SoleilQ]

macOs Monterey 12.4

[0xCCY]

works fine for me. And Windows OS too.

VS code version? In 1.7, they enabled Sandbox : https://github.com/microsoft/vscode/issues/154006 .

This changes the workbench.html from folder electron-browser > electron-sandbox which should break the extension as it is targeting the electron-browser.

This update however allows custom css and js injection without the warning prompt as it can contain any malicious injection within the sandbox. (or maybe it's because of the previous checksum fix I installed? someone verify)

I had merged and build the PR from https://github.com/EYHN/vscode-vibrancy/pull/147 and https://github.com/EYHN/vscode-vibrancy/pull/144 as a temporary solution, get it here: https://github.com/0XCCY/vscode-vibrancy/releases/tag/1.0.17

Anyone wants to take up this project? Maybe we can communicate with the author and work something out.

[nbbaataraa]

works fine for me. And Windows OS too.

VS code version? In 1.7, they enabled Sandbox : microsoft/vscode#154006 .

This changes the workbench.html from folder electron-browser > electron-sandbox which should break the extension as it is targeting the electron-browser.

This update however allows custom css and js injection without the warning prompt as it can contain any malicious injection within the sandbox. (or maybe it's because of the previous checksum fix I installed? someone verify)

I had merged and build the PR from #147 and #144 as a temporary solution, get it here: https://github.com/0XCCY/vscode-vibrancy/releases/tag/1.0.17

Anyone wants to take up this project? Maybe we can communicate with the author and work something out.

Yes. it's 1.70 version.

[illixion]

works fine for me. And Windows OS too.

VS code version? In 1.7, they enabled Sandbox : microsoft/vscode#154006 .

This changes the workbench.html from folder electron-browser > electron-sandbox which should break the extension as it is targeting the electron-browser.

This update however allows custom css and js injection without the warning prompt as it can contain any malicious injection within the sandbox. (or maybe it's because of the previous checksum fix I installed? someone verify)

I had merged and build the PR from #147 and #144 as a temporary solution, get it here: https://github.com/0XCCY/vscode-vibrancy/releases/tag/1.0.17

Anyone wants to take up this project? Maybe we can communicate with the author and work something out.

I haven't talked to the author, but I could try continuing support for this extension. I've created a fork called Vibrancy Continued, added this change and published it as a new extension: https://marketplace.visualstudio.com/items?itemName=illixion.vscode-vibrancy-continued

[Rey-Wang]

@manualmanul You have been a lifesaver! I got reborn🛟🛟🛟