#Failed to run candle.exe: Latest Tauri Version

35 messages · Page 1 of 1 (latest)

sturdy stone
#

Hello,

We've updated our app and are trying to build it for Windows. However, it seems to be failing for no reason. Here is the log/error:

Built application at: D:\a\code\code\target\release\Modrinth App.exe
Info Verifying wix package
Downloading https://github.com/wixtoolset/wix3/releases/download/wix3141rtm/wix314-binaries.zip
Info validating hash
Info extracting WIX
Info Target: x64
Running candle for "main.wxs"

failed to bundle project: error running candle.exe: failed to run C:\Users\runneradmin\AppData\Local\tauri\WixTools314\candle.exe
Error failed to bundle project: error running candle.exe: failed to run C:\Users\runneradmin\AppData\Local\tauri\WixTools314\candle.exe
D:\a\code\code\apps\app:

We're using the mainBinaryName feature. Our Tauri Version is RC17. Is anyone able to find any insight into this?

cc @wide cloud (I think this might be caused by your recent changes to the bundler)

wide cloud
sturdy stone
wide cloud
#

@sturdy stone can you try building again and after it fails, upload the file located in C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\msi\x64\main.wxs

sturdy stone
#

Ok yup doing now!

wide cloud
#

also provide tauri info output

sturdy stone
wide cloud
#

@sturdy stone are you by any chance using a custom wix template?

sturdy stone
#

Let me check

#

Don't think so

#

ah yes we are

#

let me get rid of it

#

it was for file associations but i think those are in tauri natively now

wide cloud
#

yeah they are, I think the problem is that your custom wix template was outdated because the line it errors on, is where we provide the path to main binary

The old template used {{app_binary_exe}} but we changed that to {{main_binary_path}} so the CLI didn't find main_binary_path and so it wasn't replaced with the correct path and left empty

sturdy stone
#

ahh right

#

thank you! it works now

#

actually wait it's not generating the updater signatures

wide cloud
#

did you enable createUpdaterArtifacts in config?

sturdy stone
#

Done Adding Additional Store
Successfully signed: C:\Users\jaiag\AppData\Local\Temp\nstB6AE.tmp
Signing C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\nsis\Modrinth App_0.8.8_x64-setup.exe
Signing C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\nsis\Modrinth App_0.8.8_x64-setup.exe with identity "6007d6ed9b1ba057aa29144d58ca3ed89ac4ef94"
Info "Done Adding Additional Store\r\nSuccessfully signed: C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle/nsis/Modrinth App_0.8.8_x64-setup.exe\r\r\n"
Bundling C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\msi\Modrinth App_0.8.8_x64_en-US.msi.zip
Bundling C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\nsis\Modrinth App_0.8.8_x64-setup.nsis.zip
Warn Legacy v1 compatible updater is deprecated and will be removed in v3, change bundle > createUpdaterArtifacts to true when your users are updated to the version with v2 updater plugin
Finished 2 bundles at:
C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\msi\Modrinth App_0.8.8_x64_en-US.msi
C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\nsis\Modrinth App_0.8.8_x64-setup.exe
C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\msi\Modrinth App_0.8.8_x64_en-US.msi.zip (updater)
C:\Users\jaiag\Documents\Coding\modrinth\code\target\release\bundle\nsis\Modrinth App_0.8.8_x64-setup.nsis.zip (updater)

Error Invalid symbol 92, offset 346.

Process finished with exit code 1

#

I get this error

#

it creates the updater artifact but no sig

#

nvm, my fault

#

I put in the key incorrectly

wide cloud
#

cool, let me know if there is more issues

sturdy stone
#

If you set the mainbinaryname with spaces in it

sturdy stone
#

@wide cloud Sorry for double ping, any ideas for AppImage?

#

Basically appimage doesn't allow spaces in the binary name

#

But not sure how that should work with the option

wide cloud
#

I haven't had time to investigate yet, will look into it soon