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
I just updated to latest v7.0.0 version published yesterday (previously on latest 6.x version), and I can no longer open the app window when I click on the tray icon. Nothing happens as well when I right-click on the icon. I have to use the Task Manager to close the app.
It seems the extension still work though, as I received notifications when the app started and the icon is properly colored.
Anyone knows how to disable the auto-upgrade? I keep being upgraded to the broken version
@danielpof to disable update via winget (which now has the 7.0.1) just pin the package. And to disable autoupdate it helped me to create %LocalAppData%\gitify-updater file, so the updater fails to create its working directory.
Here's the updated v6.2.0 reinstall script:
@echooffcall :log Kill Gitify
tasklist /fi "imagename eq gitify.exe"|findstr /i /b gitify.exe >nulifnoterrorlevel1call :runtaskkill /im gitify.exe ||exit /b
call :log Remove Gitify updater
ifexist"%LocalAppData%\gitify-updater"call :rundel /q /f "%LocalAppData%\gitify-updater"||exit /b
ifexist"%LocalAppData%\gitify-updater"call :runrd /s /q "%LocalAppData%\gitify-updater"||exit /b
call :log Disable Gitify updater >"%LocalAppData%\gitify-updater"||exit /b
call :log Uninstall Gitify
call :run winget uninstall -e --all-versions --id Gitify.Gitify
::: Continue if no matching package was found (-1978335212)ifnot"%errorlevel%"=="-1978335212"ifnot"%errorlevel%"=="0"exit /b %errorlevel%call :log Install Gitify 6.2.0
:installcall :run winget install --no-upgrade --silent -e --id Gitify.Gitify --version 6.2.0
::: Retry if no matching package was found (-1978335212) or package is already installed (-1978335135)::: - Winget needs few seconds after uninstall to recognize package as not installedif"%errorlevel%"=="-1978335212" ( goto :install
) elseif"%errorlevel%"=="-1978335135" ( goto :install
) elseifnot"%errorlevel%"=="0"exit /b %errorlevel%call :log Pin Gitify 6.2.0
call :run winget pin add -e --id Gitify.Gitify --version 6.2.0 ||exit /b
call :log Run Gitify 6.2.0
::: Actually start /b doesn't work here,::: gitify launches subprocess and keeps running in the current session anywaycall :runstart /b "Gitify 6.2.0""%LocalAppData%\Programs\Gitify\Gitify.exe"call :log Done
exit /b
:logecho === %*>&2
exit /b
:runecho^>^>^>%*>&2
call%*ifnot"%errorlevel%"=="0"echo^<^<^< (%errorlevel%) %*>&2 &&exit /b %errorlevel%
EDIT: Retry winget install if winget things the package is still installed
@iki thanks for the careful retest, and one correction: the electron-menubar fix was included in v7.1.0. The dependency bump (#3085) is a chore commit, so it doesn't appear in the changelog, but it's an ancestor of the v7.1.0 tag and the tag pins electron-menubar@10.1.3.
Which unfortunately tells us that fix addressed a different failure mode than yours: a post-show blur race can explain a dead left-click (the window shows, then instantly hides), but it can't explain a dead right-click, since the tray context menu never involves the window. Something on your machine is killing both, which points at either the main process stalling shortly after startup, or Windows not delivering tray events to the app at all.
Since you kindly offered to help diagnose: could you install this instrumented 7.1.0 build and share the log?
After starting Gitify, right-click works, but once I left-click, not only does the window fail to open, but right-click also stops working.
Sometimes the Gitify window opens without any interaction (or maybe from a left-click a few hours ago) in a size somewhat larger than a maximized window.
Regarding CPU usage, it stays mostly at zero after starting Gitify with no interaction or only using the right-click menu. After a left-click, it persistently stays around 4% in Task Manager on Intel Core i7-12700.
And here's the diagnostic log without timestamps and with my interaction notes(←):
[info] [diag:menubar] event 'create-window'
[info] [app updater] Starting updater
[info] [app updater] Checking for updates on application launch
[info] [auto updater] Checking for update
[info] [diag:menubar] event 'after-create-window'
[info] [diag:menubar] event 'ready'
[info] [diag:tray] listeners bound: click=1 right-click=0
[info] [auto updater] Update available
[info] [auto updater] Update downloaded
← click "Later" in updater's dialog
← right-click (works)
[info] [diag:tray] raw 'right-click' bounds={"x":2115,"y":1392,"width":33,"height":48}
← right-click (works)
[info] [diag:tray] raw 'right-click' bounds={"x":2115,"y":1392,"width":33,"height":48}
[info] [diag:heartbeat] main process event loop alive
[info] [diag:heartbeat] main process event loop alive
[info] [diag:heartbeat] main process event loop alive
← left-click (not work)
[info] [diag:menubar] event 'show'
← both right-click and left-click (not work); no logs are output at all, including heartbeat logs
Root cause found, hopefully. Thanks @Hibi-10000, your log was incredibly helpful.
The heartbeat in your trace stops immediately after event 'show' and never resumes, which pins the hang inside showWindow, between emit('show') and emit('after-show'). The only work in that span is positionWindow() and window.show().
It’s a recursion between positionWindow and the window’s resize listener: setPosition makes Windows dispatch WM_SIZE inline, which re-enters positionWindow, which calls setPosition again... forever. That single loop explains every symptom you reported: the blocked event loop (no heartbeat, and both click types dead, not just left), the sustained ~4% CPU, and the window appearing “larger than a maximized window” as each pass nudges it. It’s a regression introduced in electron-menubar v10 - the older menubar had no resize listener, which is why v6 was fine.
Could you both try this build before we release? @Hibi-10000@iki
Open https://github.com/gitify-app/gitify/actions/runs/30461528359 and download Gitify-dist-win from the Artifacts section at the bottom (you need to be signed in to GitHub)
Unzip and run the installer
Left-click the tray icon a few times, then right-click — the window should open, and right-click should keep working afterwards
The build reports itself as 7.1.1, the same as the current release, so the auto-updater will report “no update” and leave it in place.
Activity
iki commentedon Jul 23, 2026
@setchy same for me, some more info:
%AppData%\gitifyprofile + restarting => new profile is created, no change%AppData%\gitify\logs\main.log, only 2+2 lines for app/auto updater🚑 Workaround: Kill Gitify process, remove update, install Gitify 6.2.0
vincent-chtln commentedon Jul 23, 2026
@iki thanks for the complemetary info, my report was a bit thin 😅
Moved back to 6.20.0 too, app works fine.
ci: add instrumented windows build for #3064
danielpof commentedon Jul 24, 2026
Anyone knows how to disable the auto-upgrade? I keep being upgraded to the broken version
iki commentedon Jul 24, 2026
New v7.0.1 still has the issue
iki commentedon Jul 24, 2026
@danielpof to disable update via winget (which now has the 7.0.1) just pin the package. And to disable autoupdate it helped me to create
%LocalAppData%\gitify-updaterfile, so the updater fails to create its working directory.Here's the updated v6.2.0 reinstall script:
EDIT: Retry winget install if winget things the package is still installed
danielpof commentedon Jul 27, 2026
@iki Creating the
%LocalAppData%\gitify-updaterfile seem to have worked, thank.iki commentedon Jul 28, 2026
@afonsojramos the issue still happens with release v7.1.0 that didn't mention your #3085 fix, but comes later in
maincommits.Can I help you to diagnose that further?
Steps to reproduce:
del /q /f "%LocalAppData%\gitify-updater"Check for updatesin Gitify right-click tray menu%LocalAppData%\gitify-updaterand installedWorkaround: Reinstall Gitify 6.2.0, you can use the script above
ci: add windows tray diagnostic for #3064
ci: add instrumented windows build for #3064
afonsojramos commentedon Jul 28, 2026
@iki thanks for the careful retest, and one correction: the
electron-menubarfix was included in v7.1.0. The dependency bump (#3085) is achorecommit, so it doesn't appear in the changelog, but it's an ancestor of thev7.1.0tag and the tag pinselectron-menubar@10.1.3.Which unfortunately tells us that fix addressed a different failure mode than yours: a post-show blur race can explain a dead left-click (the window shows, then instantly hides), but it can't explain a dead right-click, since the tray context menu never involves the window. Something on your machine is killing both, which points at either the main process stalling shortly after startup, or Windows not delivering tray events to the app at all.
Since you kindly offered to help diagnose: could you install this instrumented 7.1.0 build and share the log?
Gitify-diag-3064-winfrom https://github.com/gitify-app/gitify/actions/runs/30370583842 (bottom of the page; needs GitHub login)%AppData%\gitify\logs\main.loghereWhat the log will tell us:
diag:heartbeatlines should appear every 30s. If they stop, the main process stalled, and the last line before the silence names the culprit.diag:tray raw 'click'lines appear when you click, Windows isn't delivering tray events to the app.diag:menubar/diag:windowlines around them will show exactly where the show/hide goes wrong.Also useful: whether
Gitify.exeshows unusual CPU in Task Manager while this happens. Thanks!Hibi-10000 commentedon Jul 29, 2026
First, FYI in my environment:
Intel Core i7-12700.And here's the diagnostic log without timestamps and with my interaction notes(
←):fix: guard positionWindow against re-entrant resize recursion (#124)
afonsojramos commentedon Jul 29, 2026
Root cause found, hopefully. Thanks @Hibi-10000, your log was incredibly helpful.
The heartbeat in your trace stops immediately after event 'show' and never resumes, which pins the hang inside showWindow, between emit('show') and emit('after-show'). The only work in that span is positionWindow() and window.show().
It’s a recursion between positionWindow and the window’s resize listener: setPosition makes Windows dispatch WM_SIZE inline, which re-enters positionWindow, which calls setPosition again... forever. That single loop explains every symptom you reported: the blocked event loop (no heartbeat, and both click types dead, not just left), the sustained ~4% CPU, and the window appearing “larger than a maximized window” as each pass nudges it. It’s a regression introduced in electron-menubar v10 - the older menubar had no resize listener, which is why v6 was fine.
Fixed in gitify-app/electron-menubar#124 (released as 10.1.5) and pulled into Gitify in #3115.
Could you both try this build before we release? @Hibi-10000 @iki
Open https://github.com/gitify-app/gitify/actions/runs/30461528359 and download Gitify-dist-win from the Artifacts section at the bottom (you need to be signed in to GitHub)
Unzip and run the installer
Left-click the tray icon a few times, then right-click — the window should open, and right-click should keep working afterwards
The build reports itself as 7.1.1, the same as the current release, so the auto-updater will report “no update” and leave it in place.
iki commentedon Jul 29, 2026
Awsome @afonsojramos 🔥 The build above works perfectly!