Myself, and especially contributors to a Tauri-based app, do not want/have the signing keys when testing. However, when the various environment variables are not set, the build just fails.
There is no quick way to build a non-signed bundle of an app.
Describe the solution you'd like
tauri build --no-sign
Alternatives considered
Currently, the workaround is to have something like a tauri.conf.dev.json file with values like:
"bundle": { "windows": null }
Then, use tauri build --config src-tauri/tauri.conf.dev.json.
I just find it odd there is no flag in the cli to disable signing.
Additional context
It is helpful to go through the whole workflow of installing, manually opening, checking the closing and re-opening behaviour, checking uninstalling (if all expected files are removed). Also, with things like the updater plugin, checking the automated update/restart workflow.
Describe the problem
Myself, and especially contributors to a Tauri-based app, do not want/have the signing keys when testing. However, when the various environment variables are not set, the build just fails.
There is no quick way to build a non-signed bundle of an app.
Describe the solution you'd like
Alternatives considered
Currently, the workaround is to have something like a
tauri.conf.dev.jsonfile with values like:Then, use
tauri build --config src-tauri/tauri.conf.dev.json.I just find it odd there is no flag in the cli to disable signing.
Additional context
It is helpful to go through the whole workflow of installing, manually opening, checking the closing and re-opening behaviour, checking uninstalling (if all expected files are removed). Also, with things like the updater plugin, checking the automated update/restart workflow.