-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[feat] Can provide an "afterBundleCommand" hook function? #9767
Comments
how and why do you need to manually sign installer? if you have setup the signing configurations correctly, we sign the installer for you. |
@amrbashir Thank you very much for your reply! I configured it correctly, and I see that tauri will sign the packaged exe application, but I still need to sign the generated NSIS setup.exe installation package. But I'm not sure if Tauri will continue to sign this setup.exe. If it can be signed, then I don't need this requirement, if not, then I want to be able to customize the script to continue signing setup.exe after the bundle produces setup.exe. |
It does sign the |
I know, thank you very much for your reply, but I still wish Tauri could add more hooks to the build process, similar to Electron, so the developer's freedom would be much better.
|
Describe the problem
Sometimes, I need to run some custom scripts after building the installer application (
{appname}-setup.exe
) and before generating the update package(such assetup.nsis.zip
orsetup.nsis.zip.sign
).This is because I need to manually sign the
{appname}-setup.exe
file, and without thisafterBundleCommand
hook, I won't be able to complete this before generating the update package.Describe the solution you'd like
Can you provide a hook "afterBundleCommand" to execute after the installer application is generated?
Alternatively, are there any alternative solutions?
Thanks alot!
Additional context
No response
The text was updated successfully, but these errors were encountered: