missioncontrol_active broken

Bugs or Unexpected Behavior
1

Note:
Before bug reporting, please make sure you have tried the latest (alpha) version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app's "Crash Reports" section.

Describe the bug
The condition missioncontrol_active shows as true at all times, regardless if Mission Control is active or not. Started with latest macOS update (Tahoe 26.4)

My condition is specifically “missioncontrol_active == 1” and it always evaluates to true.

Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):

No input device, condition.

Screenshots
If applicable, add screenshots to help explain your problem. (You can just paste or drag them here)

You can see in these screenshot that the green True indicator is on both normally and while Mission Control is active.

Screenshot1
Screenshot13276×2132 735 KB

Screenshot2MissionControl
Screenshot2MissionControl3344×2176 742 KB

Device information:

  • Type of Mac: MacBook Pro M4
  • macOS version: 26.4 (25E246)
  • BetterTouchTool version: 6.334 (2026040105)

Additional information (e.g. crash logs, related issues, etc.):

2

could you try to restart your machine? it's possible the system went into a weird state (detecting mission control active is quite tricky and requires checking for a specific window)

It still seems to work fine here on 26.4

3

I restarted my machine but it did not fi the issue.

My bad for the slow reply, after I restarted I tried troubleshooting more and then forgot to get back to you. Nothing worked.

4

Wanted to follow up and see if there's any further response? Also, a slight update with some additional information: testing shows that the condition works when an app is in fullscreen. But not when the app is running in a standard Desktop Space as a windowed application.

(I entered the BTT app into a true fullscreen Space via the green full-screen button — and tested the condition; I can confirm it toggles between true and false depending on whether Mission Control is active.)

For clarity, I'm referring to "fullscreen" as in when the application occupies its own dedicated Space — not when it is running on a standard Desktop Space with the window simply zoomed to fill the screen.)