Skip to content

Unable to open window #3064

Closed

Description

@vincent-chtln

🔍 Is there already an issue for your problem?

  • I have checked older issues, open and closed

📝 Description

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.

🪜 Steps To Reproduce

Update to 7.0.0 version

🪵 Log Excerpts

No response

Gitify Version

7.0.0

Operating System

Windows

GitHub Account

GitHub Cloud

📸 Screenshots

No response

Activity

  1. added theissue type on Jul 22, 2026
  2. iki commented on Jul 23, 2026

    @iki

    @setchy same for me, some more info:

    • happens each time
    • killing the process + removing/renaming %AppData%\gitify profile + restarting => new profile is created, no change
    • no errors in %AppData%\gitify\logs\main.log, only 2+2 lines for app/auto updater
      [2026-07-23 10:42:47.161] [info]  [app updater] Starting updater
      [2026-07-23 10:42:47.164] [info]  [app updater] Checking for updates on application launch
      [2026-07-23 10:42:47.164] [info]  [auto updater] Checking for update
      [2026-07-23 10:42:48.777] [info]  [auto updater] Update not available

    🚑 Workaround: Kill Gitify process, remove update, install Gitify 6.2.0

    taskkill /im gitify.exe
    del /s /q /f "%LocalAppData%\gitify-updater"
    winget uninstall -e --all-versions --id Gitify.Gitify
    winget install -e --id Gitify.Gitify --version 6.2.0
  3. vincent-chtln commented on Jul 23, 2026

    @vincent-chtln
    Author

    @iki thanks for the complemetary info, my report was a bit thin 😅
    Moved back to 6.20.0 too, app works fine.

  4. danielpof commented on Jul 24, 2026

    @danielpof

    Anyone knows how to disable the auto-upgrade? I keep being upgraded to the broken version

  5. iki commented on Jul 24, 2026

    @iki

    New v7.0.1 still has the issue

  6. iki commented on Jul 24, 2026

    @iki

    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:

    @echo off
    
    call :log Kill Gitify
    tasklist /fi "imagename eq gitify.exe" | findstr /i /b gitify.exe >nul
    if not errorlevel 1 call :run taskkill /im gitify.exe || exit /b
    
    call :log Remove Gitify updater
    if exist "%LocalAppData%\gitify-updater" call :run del /q /f "%LocalAppData%\gitify-updater" || exit /b
    if exist "%LocalAppData%\gitify-updater" call :run rd /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)
    if not "%errorlevel%"=="-1978335212" if not "%errorlevel%"=="0" exit /b %errorlevel%
    
    call :log Install Gitify 6.2.0
    :install
    call :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 installed
    if "%errorlevel%"=="-1978335212" ( goto :install
      ) else if "%errorlevel%"=="-1978335135" ( goto :install
      ) else if not "%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 anyway
    call :run start /b "Gitify 6.2.0" "%LocalAppData%\Programs\Gitify\Gitify.exe"
    
    call :log Done
    exit /b 
    
    :log
    echo === %*>&2
    exit /b
    
    :run
    echo ^>^>^> %*>&2
    call %*
    if not "%errorlevel%"=="0" echo ^<^<^< (%errorlevel%) %*>&2 && exit /b %errorlevel%

    EDIT: Retry winget install if winget things the package is still installed

  7. added
    help-wantedExtra attention is needed
    priority:highItems of high importance. Applicable to all users or use-cases
    on Jul 24, 2026
  8. danielpof commented on Jul 27, 2026

    @danielpof

    @iki Creating the %LocalAppData%\gitify-updater file seem to have worked, thank.

  9. iki commented on Jul 28, 2026

    @iki

    @afonsojramos the issue still happens with release v7.1.0 that didn't mention your #3085 fix, but comes later in main commits.

    Can I help you to diagnose that further?

    Steps to reproduce:

    1. Re-enable Gitify updater (if it was disabled above): del /q /f "%LocalAppData%\gitify-updater"
    2. Run Check for updates in Gitify right-click tray menu
    3. When the update 7.1.0 is ready, quit Gitify and start it again
      • ✅ Gitify 7.1.0 was downloaded to %LocalAppData%\gitify-updater and installed
      • ✅ Gitify 7.1.0 displayed notification after start
      • ❌ Gitify 7.1.0 still does not visibly react on left/right-click on tray icon

    Workaround: Reinstall Gitify 6.2.0, you can use the script above

  10. afonsojramos commented on Jul 28, 2026

    @afonsojramos
    Member

    @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?

    1. Download Gitify-diag-3064-win from https://github.com/gitify-app/gitify/actions/runs/30370583842 (bottom of the page; needs GitHub login)
    2. Install it (it's unsigned, so SmartScreen will warn: "More info" then "Run anyway")
    3. Let it run for a minute or two, clicking and right-clicking the tray icon a few times
    4. Attach %AppData%\gitify\logs\main.log here

    What the log will tell us:

    • diag:heartbeat lines should appear every 30s. If they stop, the main process stalled, and the last line before the silence names the culprit.
    • If heartbeats continue but no diag:tray raw 'click' lines appear when you click, Windows isn't delivering tray events to the app.
    • If raw clicks do appear, the diag:menubar / diag:window lines around them will show exactly where the show/hide goes wrong.

    Also useful: whether Gitify.exe shows unusual CPU in Task Manager while this happens. Thanks!

  11. Hibi-10000 commented on Jul 29, 2026

    @Hibi-10000

    First, FYI in my environment:

    • 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
    
  12. afonsojramos commented on Jul 29, 2026

    @afonsojramos
    Member

    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.

  13. iki commented on Jul 29, 2026

    @iki

    Awsome @afonsojramos 🔥 The build above works perfectly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp-wantedExtra attention is neededplatform:windowsRelated to windows buildpriority:highItems of high importance. Applicable to all users or use-cases

    Type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions