Open tylerbrandt opened 2 years ago
I have just experienced the same behaviour. As it turned out, this happens if the filename contains spaces (or probably any other character that cannot be used in a GitHub release asset). GitHub renames the file automatically and uses a .
instead of the space character (see #1759).
I fixed it by renaming the .exe
file created such that it no longer contains spaces. Now it‘s working the same way as with the macOS packages.
Pre-flight checklist
Electron Forge version
6.0.0-beta.61
Electron version
v15.3.0
Operating system
windows-latest (GitHub Actions)
Last known working Electron Forge version
No response
Expected behavior
When publishing Mac files, if the files already exist in the release, they are either ignored or silently overwritten (it's not clear which). I would expect the same to happen when publishing Windows files.
Actual behavior
If the release doesn't exist or doesn't have Windows files in it already, the publisher works fine. If it does exist and have Windows files, I see the incredibly verbose error log shown in Additional Info. Even though it looks like an internal GitHub error, I consistently see this issue only when attempting to republish existing releases (for example to test a new release workflow).
Steps to reproduce
electron-forge publish
electron-forge publish
Additional information
Log from failing publish:
Occasionally we get the a more direct error than the above (I'm not sure what causes it to be one or the other):