Unable to delete output folder via Finder when tmpdir=true
See original GitHub issueWhen packaging an app on OS X (v10.11.4) using the default settings for out
and tmpdir
, the resulting [product name]-darwin-x64
output folder cannot be deleted via Finder. When attempting to delete it, Finder asks for an admin password, but then fails with a permissions error message. However, the folder appears to be properly owned and accessible to me, and I can delete it just fine via terminal with normal user privileges.
I discovered that if I use the --tmpdir=false
option, I can delete the output folder just fine, so this issue seems to be related to the fs.move
call in moveApp
of common.js
(so maybe it’s actually a problem with fs-extra
?). It’s certainly not a major issue, but I’m curious to know what’s causing it! Any ideas?
Which version of electron-packager are you using?
7.0.2
What CLI arguments are you passing? Alternatively, if you are using the API, what parameters are you passing to the
packager()
function?
electron-packager . product-name --platform=darwin --arch=x64 --osx-sign.identity="[signing identity]" --ignore="[regex galore]" --download.strictSSL=true --icon design/icon.icns
What version of Electron are you building with?
1.0.2
What is the host platform are you running electron-packager on?
OS X El Capitan v10.11.4 (15E65)
What target platform(s)/architecture(s) are you building for?
--platform=darwin --arch=x64
Is there a stack trace in the error message you’re seeing?
N/A
Please provide either a failing testcase or detailed steps to reproduce your problem.
- Package an application without specifying the
out
ortmpdir
flags - Attempt to delete the resulting output folder via Finder
Issue Analytics
- State:
- Created 7 years ago
- Reactions:21
- Comments:12 (5 by maintainers)
This was super demotivating, thanks a lot for your analysis @giilby --tmpdir=false seems like a good solution
Whenever something like this happens on OSX, it triggers my paranoia, hope this gets solved and others don’t experience the same thing too, just wasted 45 minutes in anxiety until I found this issue
Same problem here, MacOS Sierra 10.12.3. Can only remove the folder using bruteforce
sudo rm -rf [foldername]