-
-
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
How to debug & log NSIS? #4712
Comments
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still relevant, please don't close |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
reopen please... still very important |
Any update on this? |
Why closed? |
Followup on #4711 that I think deserves its own issue.
Is there any way to figure out what went wrong with NSIS installs, updates, uninstalls? Having no ability to log or get any error messages makes it difficult to rely on it in production - getting user log info is hard as it is. Am I missing something or is there just no way to detect errors with it?
I'm using the following setup although I don't think it's relevant to any particular version:
package.json versions:
"electron": "^8.0.0",
"electron-builder": "^22.3.2"
"electron-updater": "^4.2.0"
NSIS build seutp:
"nsis": {
"oneClick": false,
"allowToChangeInstallationDirectory": true,
"perMachine": false
}
The text was updated successfully, but these errors were encountered: