You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCode Version: Version 1.3.0-insider (1.3.0-insider) 6bc81df
OS Version: OS X 10.11.5
Steps to Reproduce:
A message pops up saying there's a new version and Insiders will be updated after it restarts.
Click 'Update Now'. Code closes but doesn't reopen even after waiting a very long time.
After manually reopening it it's still on the previous version
This has been happening for the last few weeks so it isn't a recent development, but with the daily builds now it's a little more annoying. Downloading the most recent version from the website and replacing it works fine. The stable build of Code I have installed does the automatic update fine. I have both builds installed in my Applications folder.
Thanks Julian A (@jagloro) it is definitely related to that dir, also for vscode insiders.
After: sudo chown $USER ~/Library/Caches/com.microsoft.VSCodeInsiders.ShipIt/*
vscode update complained that my copy was corrupted and advised to reinstall.
Instead I did a: rm -rf ~/Library/Caches/com.microsoft.VSCodeInsiders.ShipIt
And that did the trick for me.
Joao - please lock the discussion now, so we don't bury it further. Other similar installation/update problems can be reported in other issues, to keep the threads more separate.
Activity
joaomoreno commentedon Jun 9, 2016
Does it always happen? In other words, was an Insider update never successful for you?
scottste commentedon Jun 9, 2016
João Moreno (@joaomoreno) As far as I can remember it's always happened with the insiders build and has never been successful.
joaomoreno commentedon Jun 9, 2016
Have you ever opened Code with
sudo?scottste commentedon Jun 9, 2016
Not that I remember. Is there a way I can check to see if I did and fix it?
joaomoreno commentedon Jun 10, 2016
Basically, you can check the permissions of
~/.vscode-insidersand~/Library/Application Support/Code - Insiders.scottste commentedon Jun 10, 2016
~/.vscode-insiders-drwxr-xr-x 7 myusername~/Library/Application Support/Code - Insiders-drwx------ 10 myusernameI tried removing both of those folders and reinstalling an insiders build from a couple of days ago and it still won't update.
139 remaining items
UncleVic commentedon May 5, 2017
I've again got message
"Could not create temporary directory: Permission denied."
I did chow and xattr before. But it was showed again.
Version 1.11.2
masOS Sierra
I downloaded version 1.12 and replace it old version. Error message hasen't displayed.
Roscoechen commentedon May 7, 2017
It works for me, too!
jagloro commentedon May 11, 2017
Tried various things in this Issue. This is the one that worked for me.
(I've never had this much difficulty updating software. I hope this is fixed in the future)
rikkert commentedon May 12, 2017
Thanks Julian A (@jagloro) it is definitely related to that dir, also for vscode insiders.
After:
sudo chown $USER ~/Library/Caches/com.microsoft.VSCodeInsiders.ShipIt/*vscode update complained that my copy was corrupted and advised to reinstall.
Instead I did a:
rm -rf ~/Library/Caches/com.microsoft.VSCodeInsiders.ShipItAnd that did the trick for me.
perlun commentedon May 12, 2017
This is the fix suggested by João Moreno (@joaomoreno) which has been working for most of us, most of the time.
Joao - please lock the discussion now, so we don't bury it further. Other similar installation/update problems can be reported in other issues, to keep the threads more separate.
joaomoreno commentedon Sep 27, 2018
This is due to a well known Squirrel issue: Squirrel/Squirrel.Mac#182
Workaround: Move Code out of Downloads and into the Applications folder.
Workaround 2: If updates still don't work after moving Code to the Applications folder, you can fix it with
xattr:Closing this issue since the fix for #57664 allows us to inform users of this situation, instead of failing silently.
fixes microsoft#7426