Open hatton opened 3 years ago
Electron-builder Version: 22.9.1 OS: windows 10 Node: 12.14.0
C:\dev\lameta\node_modules\.bin\electron-builder --win --x64 • electron-builder version=22.9.1 os=10.0.18363 • loaded configuration file=package.json ("build" field) • writing effective config file=release\builder-effective-config.yaml • packaging platform=win32 arch=x64 electron=10.1.0 appOutDir=release\win-unpacked ⨯ cannot execute cause=exit status 1 errorOut=Fatal error: Unable to commit changes command='C:\Users\hatto\AppData\Local\electron-builder\Cache\winCodeSign\winCodeSign-2.6.0\rcedit-x64.exe' 'C:\dev\lameta\release\win-unpacked\lameta.exe' --set-version-string FileDescription lameta --set-version-string ProductName lameta --set-version-string LegalCopyright 'Copyright © 2020 lameta' --set-file-version 0.9.2 --set-product-version 0.9.2.0 --set-version-string InternalName lameta --set-version-string OriginalFilename '' --set-version-string CompanyName lameta --set-icon 'C:\dev\lameta\build\windows.ico' workingDir= • Above command failed, retrying 3 more times
Based on a similar report here https://github.com/electron/electron-packager/issues/590, I excluded rcedit-x64.exe from Windows Defender. Also just turned off defender entirely. No improvement.
I'm not actually doing an code signing. Not using docker or anything else interesting. I've used electron-builder for years and but I haven't run it in a few weeks (may have upgraded some component) and it just started giving me this error.
Any ideas for troubleshooting this?
Restart your computer or do this: https://github.com/electron/electron-packager/issues/590#issuecomment-1416237580
Electron-builder Version: 22.9.1 OS: windows 10 Node: 12.14.0
Based on a similar report here https://github.com/electron/electron-packager/issues/590, I excluded rcedit-x64.exe from Windows Defender. Also just turned off defender entirely. No improvement.
I'm not actually doing an code signing. Not using docker or anything else interesting. I've used electron-builder for years and but I haven't run it in a few weeks (may have upgraded some component) and it just started giving me this error.
Any ideas for troubleshooting this?