-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app-builder fails to find icons unless buildResources path is specified #2570
Comments
|
So, build process doesn't hang, but default electron icon is used, right? |
Thanks, I updated the description. |
And no, the build process does hang - it just stops with the debug output shown above, or without debug it stops at: |
Please try electron-builder 20.0.3 and please set env DEBUG=electron-builder and attach log of the terminal output. |
Same issue. Here is the end of the debug output till it hangs:
Then when I press ctrl+c I get:
|
OS? Linux? Version? Distro? |
Local: Ubuntu 16.04, icnsutils 0.8.1-1 |
Same here while trying to build snap package on macOS with I believe it was broken since Had no issues with building package with previous |
Same issue here. Copied icons from my ./app/resources into default ./build to make it work again. |
debug output looks normal then ends with this, after which there is no progress:
When I kill the process with ctrl+c I get more info:
Error: Exit code: null. Command failed: /home/mike/.cache/electron-builder/app-builder/app-builder-v0.6.1-x64/app-builder icon --format set --root /home/mike/TagTime-desktop/build --root /home/mike/TagTime-desktop --input icons --input /home/mike/TagTime-desktop/resources/icon.icns --input /home/mike/TagTime-desktop/node_modules/electron-builder-lib/templates/linux/electron-icons
• tried resolved path, but got error error=stat /home/mike/TagTime-desktop/build/icons: no such file or directory path=/home/mike/TagTime-desktop/build/icons
...
It tries to resolve several more paths, each failing.
My package.json doesn't specify any icons for Linux, here's the config:
If I add in a
"directories": {"buildResources": "resources"}
entry and create anicon.png
file in that directory then it works. Perhaps this is intended behaviour? Though it feels like a regression as there was no major version number change, and the docs says that a Linux icon can be generated from the icns file.The text was updated successfully, but these errors were encountered: