-
Notifications
You must be signed in to change notification settings - Fork 261
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
Squirrel shortcut target is not correct, app launches after install but shortcut does nothing. #238
Comments
I think I found the issue: |
I still have the same issue, I've tried to change this:
to this: but it didn't work. Is there another solution for this problem? |
@robinxshooter
Here is my full squirrelHandler.js Make sure you call it in your index.js Good luck! |
@boid-com is there a way to debug that? If i |
… On Fri, Feb 19, 2021 at 8:24 AM Leonardo Rick ***@***.***> wrote:
@boid-com <https://github.com/boid-com> is there a way to debug that? If
i start the application I can see all information, but after building the
setup file I don't know where am I supposed to to all the console.log I
have inside index.js
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHGS4R6XK6KSSHKPP2CHNJTS7ZYDNANCNFSM4EZHFEVQ>
.
--
John Heeter
Founder @ Boid.com
|
Seeing this issue with electron-forge squirrel maker, which is defined here: https://github.com/electron-userland/electron-forge/blob/master/packages/maker/squirrel/src/MakerSquirrel.ts What changes need to be made to fix this? |
The wrapper was not opening my application either, when I was using this via electron-forge. Changing my app's version in package.json from "0.0.0" to "0.0.1" resolved the issue for me. Maybe there are restrictions on the version field in the wrapper application? |
Node v8.9.4
electron-forge app with default settings no asar
Windows squirrel installer. May be related to #788
Issue is that when I build executable and run it, the app installs correctly and starts on first instance. When I close the app and start it again, it doesn't work, app does not get launched.
I believe that I am handling squirrel and app.quit() events correctly:
if (require('electron-squirrel-startup')) app.quit()
and
The application works as expected in dev mode and also when running the packaged exe directly (before it's packed into the squirrel installer).
The problem is only apparent when running the squirrel installed application.
After doing some more research, I found that the issue is that the created shortcut points to an executable that is not inside a version folder. It's the same problem described in this issue.
#169
I'm still looking into exactly what configuration options needs to be adjusted, as I'm just using electron-forge defaults.
Squirrel logs:
"forge": { "make_targets": { "win32": ["squirrel"], "darwin": ["dmg"], "linux": ["deb", "rpm"] }, "electronPackagerConfig": { "asar": false, "icon": "./logo", "packageManager": "npm", "name": "<%= productName %>" }, "electronWinstallerConfig": { "name": "<%= productName %>" }, "electronInstallerDebian": {}, "electronInstallerRedhat": {}, "github_repository": { "owner": "", "name": "" }, "windowsStoreConfig": { "packageName": "", "name": "electroboid" } }
The text was updated successfully, but these errors were encountered: