Environment:
Tangrid version: 1.5.6 (not the first version I observed this issue, maybe start from 1.5.2)
Application: WeChat for macOS (com.tencent.xinWeChat)
OS: macOS 26.6 (25G72)
Description:
When I click the red close button (“X”) on the main WeChat window, WeChat should remain running in the background. Instead, Tangrid sends a quit AppleEvent to WeChat shortly after the window is closed, causing the entire WeChat process to exit.
This is not a WeChat crash. macOS reports a normal voluntary process exit, and no WeChat crash report is generated.
Steps to reproduce:
Launch WeChat while Tangrid is running.
Click the red “X” button on the main WeChat window.
Wait approximately one second.
Observe that WeChat exits completely instead of remaining active in the background.
Expected behavior:
Closing the main WeChat window should only remove that window. Tangrid should update its window-management state without terminating the application.
Actual behavior:
Tangrid observes the window-destroyed event and then sends an application-level quit event to WeChat approximately 0.8 seconds later. WeChat and its helper processes subsequently terminate.
Evidence:
The issue was reproduced twice in the latest log:
10:57:27.925 — Tangrid observes the WeChat window being destroyed.
10:57:28.252 — Tangrid confirms the window lifecycle has ended.
10:57:28.756 — Tangrid sends AESendMessage(aevt,quit ... target=WeChat).
10:57:28.973 — The WeChat main process exits.
The same sequence occurs again
Relevant macOS unified-log entries:
Tangrid ... AESendMessage(aevt,quit ... target='psn '[微信])
WeChat ... RECEIVED:(aevt,quit) ... target=Tangrid
WeChat ... Handling Quit AppleEvent
The consistent delay between the window-destroyed event and the outgoing quit event suggests that Tangrid may be incorrectly treating the destruction of WeChat’s main window as a request to terminate the entire application.
