Insomnia Windows app opens up a new app and disables shortcut
Expected Behavior
Double click the shortcut Insomnia opens up No separate app is opened The shortcut is still active and working.
Actual Behavior
Double click the shortcut Insomnia opens up in a separate app/window and the shortcut is not working anymore. The error shown when the shortcut is clicked,
Reproduction Steps
install insomnia open the app pin the short cut to the taskbar click the short cut on the task bar to open the app to see the app open in a separate window and then click the short cut again to get the error
Is there an existing issue for this?
- [x] I have searched the issue tracker for this problem.
Which sync method do you use?
- [ ] Git sync.
- [ ] Insomnia Cloud sync.
- [x] Local only
Additional Information
This is the taskbar after clicking the pinned shortcut.
Insomnia Version
11.0.1
What operating system are you using?
Windows
Operating System Version
Windows 11
Installation method
download the app from insomnia and install
Last Known Working Insomnia version
not sure but the version before this 11 release and new look and feel.
동일한 문제가 발생했습니다.
the same report here.
same for me
it was created a new folder version in my computer, so i opened the "stable" version and work.
the same report here.
@carllabuschagne thank you for the report.
We're tracking the Windows launch issues here: https://github.com/Kong/insomnia/issues/8537
There's a PR up to fix this. I'll update here when it's released
I've re-opened this issue because the shortcut problem is likely going to stick around for a bit. We're working on moving away from using Squirrel for portable installs due to security vulnerabilities, and have a stopgap in place that makes the taskbar shortcut unusable.
In the meantime, there's a beta that should prevent that error dialog from cropping up when launching, would you mind giving it a try? https://github.com/Kong/insomnia/releases/tag/core%4011.0.2-beta.0
Hi, I'm also facing the same issue on my Windows machine. I tried the 11.0.2 version and the 11.1.0-beta1 and both still have the same issue.
I am downgrading to v11.0.0 for now. Let me know if you need more info from me.
still the same here with 11.3.0