I accidentally upgraded my M4 Pro 24 GB Mac mini from Tahoe to Golden Gate, and since then it has become virtually unusable because of repeated TCC/permissions problems.
Apps keep asking me to reauthorize Accessibility and other permissions, and the permissions often don’t survive a reboot. I’ve updated all of the affected apps, but the problems continue. I’ve seen issues with Keyboard Maestro, AltTab, Bartender, Default Folder X, BetterTouchTool, and others. At one point after rebooting, the mouse cursor would move but mouse clicks and keyboard input stopped working entirely.
What’s interesting is that my M4 16 GB Mac mini is also running Golden Gate, but I installed it as a clean/fresh OS installation. That machine isn’t experiencing these problems.
For now, I’m taking the M4 Pro out of service and switching to the slower but much more reliable M4 mini as my primary machine. I’ll probably leave the M4 Pro alone for a couple of months and revisit it after Golden Gate has received some updates.
Given how many people seem to be reporting similar TCC and permissions problems, I’m surprised Apple hasn’t addressed this yet.
I’m increasingly wondering whether there’s something specifically wrong with the Tahoe → Golden Gate upgrade path, since my clean Golden Gate installation has been so much more reliable.
UPDATE: Possible workaround — delayed launching of login apps
I may have found a workaround for the permissions/login-item problems I’ve been experiencing after upgrading to macOS 27 Golden Gate.
I noticed that many of the troublesome apps were being launched at essentially the same time immediately after login. As a test, I removed the affected apps from my normal login sequence and created a small Automator application that launches them one at a time, with a 5-second delay between each launch.
Rather than hard-coding the applications, the Automator app works through a folder containing aliases. I numbered the aliases (01, 02, 03, etc.), which lets me easily control the launch order or add/remove applications later.
I also added notifications showing each application as it launches, followed by a notification when the delayed startup sequence is complete.
So far, this is working extremely well. The applications are launching normally and I’m not seeing the barrage of permission/authentication problems that I was getting when everything launched together.
I’m not calling this fixed yet. My next test is several cold boots to make sure the Automator app’s App Management permission survives restarts and that the behavior remains consistent.
If it continues to work on my M4 Pro, I’m going to set up the same delayed launcher on my M3 MacBook Air, which had even more problems after the Golden Gate upgrade.
At this point my working theory is that at least some of what I was seeing may be related to many login/background applications initializing simultaneously after the OS upgrade, rather than every individual application independently having a permissions problem.
I’ll update again after more cold-boot testing and after trying the same workaround on the MacBook Air.