Windows: Duplicated icon in notification/status area

[Chealer]

• I am on the latest ActivityWatch version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• OS name and version: Microsoft Windows 10

• ActivityWatch version: 0.12.2

Describe the bug

I have been getting 2 icons for ActivityWatch in Windows' taskbar's notification area (aka "system tray") for a while. Both are usable, and offer "Quit ActivityWatch", which gets rid of one of them, but not the other. However, the duplication comes back every time Windows is restarted.

I am 99% confident that this started the last time I upgraded ActivityWatch. I went from 0.12.0 to 0.12.2. So while I did not verify, there are good chances that installing 0.12.0 then installing 0.12.2 would suffice to reproduce.

[github-actions]

Hi there!
As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct.
Thanks a bunch for opening your first issue! 🙏

[ErikBjare]

You probably have double startup entries. I'm not sure what causes it (maybe the installer?), but I've seen it happen before.

You can probably fix this by checking your autostart applications, and removing the duplicate entry.

[Chealer]

I do have a duplicated entry in "Applis de démarrage". The list can be accessed via Settings ->Apps -> Startup tab, or in the Startup tab of the task manager (Windows 10).
The duplication seems unavoidable as entries cannot be removed, but one of the entries can be disabled. I randomly chose which one to disable as I could not see a difference between both (they both point to the same executable), and that did allow a lasting workaround.

[Sucareto]

I'm having the same problem.
Repeated execution of aw-qt.exe triggers this error.
Maybe it needs to be checked when starting aw-qt.exe to avoid running multiple instances?

[ErikBjare]

I thought I'd fixed this already, but in the installer config file we had an extra { in the AppId which may have caused duplicate startup entries.

Fixed in 7aeb31c, will be in the next beta (yet unreleased v0.12.3b17). Hopefully the issue will now finally be resolved.

However, you will probably have the same issues when upgrading to the next release (and you need to remove the extra startup entry manually), but any upgrades after that should hopefully work now. Fingers crossed 🤞

This issue is also probably a duplicate of #813

[ErikBjare]

It did not fix it, and lead to a build error. Investigating.