Skip to content
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

After enabling monkey patch my vscode is not visible anymore on MacOs #56

Closed
felixele217 opened this issue Dec 8, 2022 · 31 comments · Fixed by #58
Closed

After enabling monkey patch my vscode is not visible anymore on MacOs #56

felixele217 opened this issue Dec 8, 2022 · 31 comments · Fixed by #58

Comments

@felixele217
Copy link

felixele217 commented Dec 8, 2022

These are my CustomizeUI Settings

image

I have MonkeyPatch and CustomizeUI enabled and after enabling Monkey Patch, my VSCode is not visible anymore after opening.

image

Anyone else having this issue?

@Sinderella
Copy link

Probably iocave/customize-ui#156

@tsukinoko-kun
Copy link

tsukinoko-kun commented Dec 8, 2022

Same Problem here 🙋‍♂️

MacBook Pro 2022 M2

@mayronH
Copy link

mayronH commented Dec 8, 2022

The only solution for now is to either uninstall MonkeyPatch + CustomizeUI or just reinstall vscode 1.73.1 and disable automatic updates.

https://code.visualstudio.com/updates/v1_73

@zsy619
Copy link

zsy619 commented Dec 9, 2022

Same Problem here 🙋‍♂️
12.6.2 (21G320)

vscode Version: 1.74.0 (Universal)

@b-lov
Copy link

b-lov commented Dec 9, 2022

same problem on M1 MacBook Air. I uninstalled customize-ui and monkey-patch extensions via commandline with code --uninstall-extension ... and got a success message, I also deleted both extension folders from ~/.vscode/extensions. Still when I try to launch vscode it remains invisible. When launching it with the --verbose tag it still says 'Loading monkey-patch'. Launching with --disable-extensions also doesn't work. Does anyone have an idea how to prevent it from trying to load monkey patch and get it to start without completely reinstalling?

@knopp
Copy link
Collaborator

knopp commented Dec 9, 2022

You need to re-install vscode at this point. Just the app bundle, your settings, extension etc will remain untouched.

@G33kNoob
Copy link

same issue

@binaryben
Copy link

Same issue here on Codium running Ventura

@GJRobert
Copy link

You need to re-install vscode at this point. Just the app bundle, your settings, extension etc will remain untouched.

Which version of VS Code to re-install, please?

@b-lov
Copy link

b-lov commented Dec 11, 2022

if you want to use monkey patch, 1.73. If you want the newest version without monkey patch, just reinstall the newest version and disable monkey patch. if you have homebrew, you can just go brew reinstall --cask visual-studio-code and disable monkey patch on next startup. if you want an earlier version, you have to download it manually.

@forivall
Copy link
Contributor

Hey, I have a basic fix submitted as a PR at #58 so that it shouldn't hose your vscode install anymore.

@pm0u
Copy link

pm0u commented Dec 16, 2022

@b-lov I get no cask exists with name 'code' when I try to run that.

The recommended formulae appears to be: brew install --cask visual-studio-code

https://formulae.brew.sh/cask/visual-studio-code#default

@b-lov
Copy link

b-lov commented Dec 18, 2022

@b-lov I get no cask exists with name 'code' when I try to run that.

The recommended formulae appears to be: brew install --cask visual-studio-code

https://formulae.brew.sh/cask/visual-studio-code#default

sorry, you're right. i fixed the typo. you can use reinstall instead of install if you had it installed before and it stopped working after the update.

@josegus
Copy link

josegus commented Dec 20, 2022

Same here, I'm using Ubuntu 22.04

@danilinus
Copy link

Same here, I'm using Mac OS Monterey 12.6

@julienaub
Copy link

Same here. I had to uninstall VSCode and reinstall it so that Monkey Patch gets disabled.

@IJuanI
Copy link

IJuanI commented Jan 13, 2023

Same here with Mac OS Monterey 12.3

@pm0u
Copy link

pm0u commented Jan 13, 2023

any progress on this? I have vscode locked to 1.73 but some extensions are now requiring 1.74 so I'd love to be able to update vscode and use all my preferred extensions.

@knopp knopp closed this as completed in #58 Jan 18, 2023
@pm0u
Copy link

pm0u commented Jan 24, 2023

I just re-enabled auto updates since this was marked resolved, updated to 1.74 and my vscode broke again, I don't believe this is resolved --

Loading monkey-patch
(node:51000) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'crypto')
    at P (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:25:24056)
    at i (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:25:33504)
    at get mainIPCHandle (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:32:6945)
    at p.<computed> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:3:53298)
    at Oe.c (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:84:7310)
    at Oe.b (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:84:5809)
    at Oe.a (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:84:4864)
    at Oe.main (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:84:4709)
    at Object.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:85:1732)
    at s._safeInvokeFunction (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:1337)
    at s._invokeFactory (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:1522)
    at s.complete (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:1801)
    at s._onModuleComplete (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:1112)
    at s._onModuleComplete (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:1358)
    at s._resolve (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:510)
    at s.defineModule (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:6066)
    at n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:10527)
    at Object.R (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:6036)
    at s._safeInvokeFunction (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:1337)
    at s._invokeFactory (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:1522)
    at s.complete (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:1801)
    at s._onModuleComplete (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:1112)
    at s._onModuleComplete (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:1358)
    at s._resolve (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:510)
    at s.defineModule (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:5:6066)
    at y (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:6:1825)
    at h (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:2554)
    at Object.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.nls.js:3:61)
    at e._createAndEvalScript (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:2598)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:2237
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js:82:14
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
(Use `Electron --trace-warnings ...` to show where the warning was created)
(node:51000) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

@The-Compiler
Copy link

@pm0u Issues in development repos are typically closed when a fix is merged into the master/main branch - that happened a week ago, but the last release is from October. So unless you're packaging/running the extension from the git repository, you won't have the change yet.

@pm0u
Copy link

pm0u commented Jan 24, 2023

@The-Compiler thanks for the clarification. I didn't see any releases on this repo so I assumed the extension just tracked master.

@binaryben
Copy link

Does the upcoming fix mean Customize UI will work again?

@The-Compiler
Copy link

@binaryben no, see the PR description in #58

@electrovir
Copy link

electrovir commented Feb 17, 2023

I've been using monkey-patch for months and suddenly today I'm now running into this issue. Why was it not a problem until now?

@GJRobert
Copy link

I've been using monkey-patch for months and suddenly today I'm now running into this issue. Why was it not a problem until now?

@electrovir perhaps you have not updated your VS Code for long until today.

It has to do with VS Code upstream, not problem of Monkey Patch / Custom UI.

@hugobiais
Copy link

For those of you who have to reinstall VS Code like I did, I would suggest making a copy of your settings.json file before uninstalling the broken version. The file can be found at ~/Library/Application\ Support/Code/User/settings.json. Then, once you have reinstalled VS Code, just copy your old settings.json into the new one (You might not have to if you had Sync Settings already on).

@saepien
Copy link

saepien commented Mar 12, 2023

Same thing just happened to me. Had to download/reinstall VSCode and removed both Customize Ui and Patch Monkey. Any update on a fix? Would be nice to not squint to read (sidebar) debugger panels.

@GJRobert
Copy link

@saepien you can read the whole thread, there is a fix no need to reinstall VSCode but I never tried anyway because I reinstalled in the first days. And seems to fix for Monkey Patch to work in 1.74+.

@vx17rt
Copy link

vx17rt commented Mar 31, 2023

  • (optional) Copy everything from /Users/:user/Library/Application Support/Code/User
  • Download 1.73 https://code.visualstudio.com/updates/v1_73
  • Move it to the Applications folder (Keep Both)
  • Move Visual Studio Code to Trash
  • Rename Visual Studio Code 2 to Visual Studio Code

@GJRobert
Copy link

I have switched to VSCodium 1.74+ (now I'm using VSCodium 1.76.1), where a modified version of MonkeyPatch works (with Custom UI!). ☞ VSCodium/vscodium#1390 (comment)
I have migrated most of my VS Code profile settings to VSCodium with ease. (tell me to post an English version of migration if needed)

MonkeyPatch + CustomUI is essential! Please keep it guys~

@t1noo7
Copy link

t1noo7 commented Jun 3, 2024

You need to re-install vscode at this point. Just the app bundle, your settings, extension etc will remain untouched.

thank u so much much! U actually save my life!!!
Kiss U never stop bro!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.