Failed to bundle project: error running candle.exe
See original GitHub issueHey there,
two days ago building tauri for win64 on github works like charme. But since yesterday evening i get:
Finished release [optimized] target(s) in 16m 58s
Info Verifying wix package
Downloading https://github.com/wixtoolset/wix3/releases/download/wix3112rtm/wix311-binaries.zip
Info validating hash
Info extracting WIX
Info Target: x64
Running candle for "main.wxs"
failed to bundle project: error running candle.exe: error running candle.exe: ``
Seems like this occurs even when directly running “tauri build”.
Any ideas?
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
[bug] Bundling fails with 'GenericFailure'on candle.exe #4594
When I run cargo tauri info it shows that the tauri-cli is outdated in the Node.js environment, but I cannot seem to be...
Read more >Candle.exe not running for specific project while building wix ...
When I build each project separately candle.exe is running before light.exe. So preprocessor variables are processed and msi-files are correct.
Read more >jpackage fails on Windows when application name differs from ...
It seems that the .exe launcher file is written with the spaces removed, but then light.exe is expecting the spaces to be present....
Read more >Configuration - Tauri Apps
The Tauri configuration object. It is read from a file where you can define your frontend assets, configure the bundler, enable the app...
Read more >TauriのリリースビルドがWindowsの場合だけcandle ... - Minerva
... running candle for "main.wxs" info: running candle.exe Error running CLI: failed to bundle project: Shell Scripting Error:`error running ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yep, wix only supports numeric versions, so there’s nothing we can do here 😕
Yeah it has a undocumented
args
property, so you can addargs: '--verbose'
and it should work.nice and thanks for your blazing fast response.
I added some additional info to the title. If anybody is stumbling with semver + special channels in versions my solution is to just use https://github.com/actions/github-script and make some little string replacements and after that setting a “cleaned” version in the tauri.conf.json.
In general i came to this, because of this bug: https://github.com/tauri-apps/tauri-action/issues/262
I wanted to get my version from package.json in the tauri.conf.json during build. So i added the package.json path in the tauri config for the version field. But it does not work with the github action.
I ended in something like that:
The script replaces additional suffixes at the version, but requires that those nightly, beta, what ever version end with
.[0-9]+
, so we get a valid fourth place in the wix version.if you have a “tag” as version then remove the leading “v” in the version
E.g. Version v1.2.3-lorem-ipsum.4 gets to 1.2.3.4
Greetings 😃