Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Mission Control 'Switch to Desktop' shortcuts broken in macOS Golden Gate

In Golden Gate (macOS 27.0.1) my "Mission Control -> Switch to Desktop #" shortcuts are broken. This has been noted on various web sites but I don't see it here. I am not using any apps for switching, just the OS.


PROBLEM

I have 6 desktops, and switching between them quickly is imperative. Key commands (shortcuts) worked with prior macOS (e.g. Tahoe). With Golden Gate, generally only the command for Desktop 1 works. If I'm on a Terminal then doing the Switch to Desktop # command prints some characters in the Terminal, so perhaps keys are being inadvertently eaten. But if I'm in another app they still don't work, so this bug is not specific to Terminal.


TEMPORARY WORKAROUND

Desktop switching shortcuts can be temporarily restored by killing the Dock. This generally works until I leave my computer--turn my display off and back on. Then I must kill the Dock to get desktop navigation back. Doing so causes all minimized windows to become visible (no longer minimized). Perhaps this is another bug; it's very annoying.


EXPECTED

In Settings, my "Switch to Desktop #" commands do not appear to conflict with other commands. Therefore, they should work as before. Other methods of switching (Move left/right a Space or open Mission Control) are far inferior.

3 replies

There have been many issues reported here with Mission Control and Spaces on macOS 27 Golden Gate, including the issue that you mention with the keyboard shortcuts to switch Spaces, and especially regarding the way Full Screen apps and app switching are handled. Some have been resolved by identifying and removing incompatible 3rd party extensions, others are bona fide bugs. The minor point update, macOS 27.0.1, did not appear to address the more significant issues.

 

Bugs should be reported to Apple here:

Feedback - macOS - Apple

 

The first step is to go to System Settings > Keyboard > Keyboard Shortcuts (button) > Mission Control, expand the second Mission Control item by clicking the expansion caret (>) and confirm that those shortcuts are enabled.



See if the problem is present when you boot in safe mode. That process performs some system cleanup and clears caches, and also disables 3rd party extensions that may cause problems.

 

Start up your Mac in safe mode - Apple Support

 

If that does not correct the issue, test in a new user account. A newly-created user account will have all settings at default, and if the issue does not occur in that new account then it provides guidance on what may need to be changed to correct the issue.

 

Add a user or group on Mac - Apple Support

 

Once the testing is complete, the new account can easily be deleted.

 

Delete a user or group on Mac – Apple Support

 

Those steps will help to isolate the problem.


If the issue persists in safe mode and a new user account, that suggests that it's a bug that Apple needs to address. 

 

Reporting issues like this to Apple is the only way to get them fixed. They do prioritize bugs based on frequency of reports, so the more people who report it, the faster it will be addressed.

 

Personally, Mission Control is working fine for my use cases on my 16" M4 Pro MBP running 27.0.1. I have many Spaces and open windows, but use three-finger swipes to switch between Spaces, I don't use full screen apps and I don't have my apps grouped, all of which are associated with reported issues.

Certainly you can just report it and wait for Apple to provide a fix. But, for example, if the two users in another thread experiencing freezing behavior when using Stacked folders in the Dock had done that, they might have had a long wait. Both turned out to have conflicting software (crapware like BrickMyMac) running. Likewise, TechTool Monitor was found by users to cause the 'glitching' they saw in Mission Control, and uninstalling it corrected the issues.


There are always bugs in a new major macOS upgrade. Most are eventually resolved by point updates, but some point updates create new bugs. In general, MAJOR issues are going to be found and fixed before the full release. What is left that impacts the general public mainly falls into three categories:

  • Identified bugs that were not of sufficient impact/priority to fix before full release
  • New, unidentified bugs that are found by users
  • Issues caused by incompatible software/extensions installed by the user on a prior version of macOS


While there are definitely some bugs with Mission Control, by far the majority of issues people have after a major upgrade fall into that last category. 

Thank you for the ideas, I just reported this as a bug as well.


"If the issue persists in safe mode and a new user account, that suggests that it's a bug that Apple needs to address." I respectfully disagree. Requiring all users who utilize a particular feature to jump through hoops--boot into safe mode, create a dummy account, etc.--in order to address what Apple has clearly broken should not be policy.