You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just updated to latest electron-builder 7.11.2 and successfully built a Win64 NSIS target on Windows 7 (no errors/warnings given).
After running the setup.exe, I noticed the app did not auto-launch after installation. So I went to manually open the link on the desktop (and menu) and found they were broken links.
I managed to trace it back to something was released in version 7.11.1, as 7.11.0 does work (if I simply change my package.json version and npm install then build).
Looking at your release notes (and commits) it's not too obvious to me what in fact is the cause.
I've noticed the problem here. The issue is that generated NSIS package are installing files at App\Version\win-*-unpacked rather than App\Version as before, but generated shortcut tries to launch App\Version\App.exe.
I suppose the original intention of the project is to install files at App\Version, thus the behaviour observed at version 7.11.2, I mean, installing files at App\Version\win-*-unpacked, should be a regression.
dharders
changed the title
Windows App Doesn't Start / Shortcut Links Missing (after successful installation)
Windows App Doesn't Start / Shortcut Links Broken (after successful installation)
Oct 7, 2016
@lbssousa Thanks. And sorry for regression. Missed tests will be added later (it was not tested :(), for now I have fixed error. Fixed version will be released in 10 minutes.
Just updated to latest electron-builder 7.11.2 and successfully built a Win64 NSIS target on Windows 7 (no errors/warnings given).
After running the setup.exe, I noticed the app did not auto-launch after installation. So I went to manually open the link on the desktop (and menu) and found they were broken links.
I managed to trace it back to something was released in version 7.11.1, as 7.11.0 does work (if I simply change my package.json version and npm install then build).
Looking at your release notes (and commits) it's not too obvious to me what in fact is the cause.
I've attached some relevant details below.
The text was updated successfully, but these errors were encountered: