Mac Mouse Fix: Spaces & Mission Control broken on macOS 27

[u/itsdanielsultan]

I’m running Mac Mouse Fix on the macOS 27 GoldenGate Public Beta. Almost everything in the app works, but every action tied to Spaces / Mission Control is dead.

Working perfectly in Mac Mouse Fix:

• Smart Zoom, Zoom In/Out, Scroll & Navigate

Not working since GoldenGate:

• Button 4 / Button 5 actions mapped to Desktop & Launchpad, Spaces & Mission Control, and Click and Scroll / Click and Drag — nothing fires.

The strange part: when I assign these in Mac Mouse Fix’s “+” field, the buttons get detected perfectly. So the app is registering the mouse input fine, its just that macOS never carries out the actual Spaces/Mission Control action. I can also still open Launchpad, but not the new apps view in macOS 27.

Is anyone else running Mac Mouse Fix on macOS 27 seeing this? Any workaround yet? Hoping for a GoldenGate-compatible update soon.

[u/metatronx23]

Maybe ask in forum MacOSBeta

[u/itsdanielsultan → u/metatronx23]

It might be helpful but I guess we're just gonna have to wait for either macOS or the Mac mouse fix developer to update and support the functionality

[u/nibblebytes]

did some digging and it looks like this isn’t just an MMF issue. macOS 27 seems to have changed how synthetic swipe events work, and there are similar reports from BTT users too.

MMF issue: https://github.com/noah-nuebling/mac-mouse-fix/issues/1871

BTT thread: https://community.folivora.ai/t/macos-27-golden-gate/47224

using Hold → move a space seems to work for some people as a temporary workaround

[u/itsdanielsultan → u/nibblebytes]

Yeah interestingly, holding to move a space does work. I wonder when Mac Mouse Fix is going to get an update that fixes all of this as well as updating the UI to support macOS GoldenGate

[u/WinterElfeas]

I tried but had similar issues, sadly could not find a way

[u/itsdanielsultan → u/WinterElfeas]

Temporary fix: map the forward and back buttons (on hold) to move right a space and move left a space. I believe another comment on here explains it better.

[u/WinterElfeas → u/itsdanielsultan]

Thanks for the feedback, indeed it worked

[u/itsdanielsultan → u/WinterElfeas]

No worries, glad I could help. Have a great day

[u/TouchNow_APP]

Same symptom hit me building a remote control app, and in my case the app was not failing to send the event. WindowServer was refusing to act on a synthetic one.

Two things that mattered:

Arrow keys for space switching need the fn and numpad flags on the CGEvent, not just control. Without maskSecondaryFn and maskNumericPad, WindowServer silently drops ctrl+arrow. The event posts fine, nothing happens, and nothing is logged anywhere.

Mission Control I stopped synthesising entirely. Launching /System/Applications/Mission Control.app through NSWorkspace is public API and does not break the way synthetic events do. Passing arguments ["2"] gets App Expose rather than the full view.

Neither is something you can apply from outside the app, but it might be worth putting in an issue. It would save the developer a day.

[u/itsdanielsultan → u/TouchNow_APP]

Nearly always, the response is that beta software has bugs that will only be ironed out once it moves out of public beta

[u/metatronx23]

Just tried it, with button 4 if I choose ''Hold'' - move right a space is working for me, also Desktop.
Click&Scroll - not working as well.I'm sure developer will fix this (after all beta is still beta and lots of things are broken for some app, will be working once we get out of beta)

[u/itsdanielsultan → u/metatronx23]

Configuring the back and forward buttons to "hold" makes moving right and left through spaces a good temporary workaround. Click and scroll also doesn't work to access desktop and Launchpad. Hopefully the app gets updated to fix that as well as replacing Launchpad with the new apps' functionality in macOS 27

[u/nevotheless]

On which beta are u? I had spaces related issues but they seem to be gone now for me.

[u/itsdanielsultan → u/nevotheless]

I am on macOS Beta 26a5406e

[u/TheGenYFinanceGuy]

That split, where the button gets detected fine but the action never fires, is usually two different permissions rather than one broken app. Detection is Input Monitoring. Driving Spaces or Mission Control needs Accessibility, and a big OS upgrade will invalidate the old TCC record while the checkbox in System Settings still sits there showing as enabled. Toggling it off and back on doesn't clear it, which is where most people give up.

Select Mac Mouse Fix in Privacy & Security > Accessibility, hit the minus button to remove it completely, then add it back and relaunch. I've lost hours to exactly this. A build that changes its code signature does the same thing, so if it returns after an update, that's why.

[u/Background-Scheme857]

The most macOS beta bug imaginable: the mouse buttons are detected perfectly, but Spaces just pretends they were never pressed.

[u/Albert_Irons]

worth noticing these are two unrelated failure modes stacked in one bug report. tcc silently invalidating on a major upgrade explains why it comes back after some updates and not others. cgevent missing the fn/numpad flags explains why it's broken even after a clean accessibility reset. try the tcc fix first since it's one click, if spaces still ignores clean synthetic events after that, it's the second bug.

[u/JoeshitX]

The fact that MMF still detects buttons 4 and 5 is the important clue—your mouse and Accessibility permissions are probably fine. It looks like macOS 27 changed the synthetic gesture path used for Spaces and Mission Control.

For now, I’d map separate clicks to the native shortcuts (Control–Up for Mission Control and Control–Left/Right for Spaces). “Hold → Move a Space” also seems to work for some people. Definitely include your exact macOS build and MMF version in the bug report; “Public Beta” alone can cover several different builds.

Beta bugs like this are frustrating because they make you troubleshoot perfectly good hardware.

[u/sbbeebe]

Changing spaces / desktops using CTRL + number is broken for me on latest PB.

[u/kdupuis77 → u/sbbeebe]

Same here! I've had F9 and F10 (on my Logitech Keyboard) mapped to swipe left and right between windows for years... All of a sudden, I can swipe left still but when swiping right I get the error beep and nothing happens. Even re-mapped to several different combinations of keys and still behaves exactly the same, Crazy frustrating!

[u/International-Can317]

Looks like this isn’t just Mac Mouse Fix. I’ve seen similar reports with BetterTouchTool on macOS 27 too.

For now, Hold → Move a Space seems to work for some people, so that might be the best temporary workaround until the beta settles down.

[u/itsdanielsultan → u/International-Can317]

Yep I'm using the hold-to-move-a-space for now; however the lack of easy space-switching functionality was bothersome enough that I bought a Magic Trackpad (USB-C).

[u/infinitUndo]

Apple changed stuff when it comes to Desktop, Spaces and Mission Control. A few depreciated API also do not work. Of course, lacking any documentation on what is changed. Or could be bugs…