Closed kud closed 1 year ago
Thats strange, I tested it on a secondary machine just now and it worked for me.
Was this output from installing it via the commandline?
I have the same issue when trying to update from within VSCode:
2023-03-14 09:06:30.927 [error] PackageIntegrityCheckFailed: Signature: PackageIntegrityCheckFailed at yt.download (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:468) at async X.x (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760) at async X.h (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
the latest version can be installed manually by downloading and installing the vsix file.
Same problem here. See the log below:
2023-03-14 08:19:27.902 [error] PackageIntegrityCheckFailed: Signature: PackageIntegrityCheckFailed
at yt.download (vscode-file://vscode-app/snap/code/121/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:468)
at async X.x (vscode-file://vscode-app/snap/code/121/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
at async X.h (vscode-file://vscode-app/snap/code/121/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
I can only install manually by downloading and installing the vsix
file.
I use the Visual Studio Code on Ubuntu 22.04 via snap packages.
Same problem for me, Windows 11, latest VS Code.
Same problem for me.
Version: 1.76.1 Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b Date: 2023-03-08T16:32:00.131Z Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.76.1 Chrome/102.0.5005.196 Electron/19.1.11 Safari/537.36
Confirmed. Can not install/update.
Well this is bad. @alexr00 Any idea what might be going on?
Nothing has changed on my end, same publish command / token. The CLI command does take significantly longer than usual the last two times, but I get the same output as usual:
Was there a recent change in VS Code signature validation? Like a format deprecation/drop
It seems that in some cases signature verification is not working (ex. https://github.com/microsoft/vscode/issues/175733).
I've created https://github.com/microsoft/vscode/issues/175733 and the folks who know about extension signing are looking into it.
1.5.2
fixed it. Thank you.
Thanks! @ alexr00