Hacker News Reader

Comment by latexr | Hacker News Reader

Your Ableton and Logitech issues seem to be the same: screwed up access permissions. Not your fault, macOS has been sucking at it for a while. It’s not unheard of for System Settings to show you some app has some permissions, but in practice it doesn’t.

What usually works is fully resetting permissions for an app:

  tccutil reset All <APP BUNDLE ID HERE>

To find the bundle ID for an app:

  mdls -raw -name kMDItemCFBundleIdentifier <APP PATH HERE>

View on HN

There definitely is something weird with Tahoe permission system. I was trying to learn Swift and after a couple keystrokes, the banner asking for the permission to access other's app data pops up without fail. Making it almost impossible to use Swift Playground. And it's been like that for a couple months now.

https://developer.apple.com/forums/thread/808758

https://developer.apple.com/forums/thread/811796

The System Settings panel for TCC permissions has been fucked since Ventura. It never reflects reality properly and won't show managed settings either (like those granted or denyed outright by a configuration profile). So users have no idea that Firefox can't access their microphone because their device administrator explicitly denied that. The redesign of System Preferences should have raised far more alarm bells than it did, and it did raise a fuck ton of alarm bells that something utterly broken is happening in Cupertino. Along the same line as the another comment in here said, it's just that some amateur is following the "wrong rules". Like, oh, we have to have the macOS settings app look and work exactly like iOS', despite being a far more complex system with a lot more legacy components.

I am literally writing a bug report right now for 26.2, because on my Mac, for whatever reason, running tccutil reset All on com.apple.Terminal isn't removing Full Disk Access. It removes everything else (screen recording, specific folder domain access, but not FDA).

> screwed up access permissions

Bane of my existence. I have wasted so much time on various apps not having some access they need.

I did try that amongst other things. Launching Ableton via Terminal also brought up the microphone permission pop-up...for the Terminal app. One has to wonder if a System that regularly "forgets" permissions is even secure at all.

> One has to wonder if a System that regularly "forgets" permissions is even secure at all.

It does not "forget", the permissions are limited to 30 days. So you have to re-grant them periodically.

Oh, and if you miss the popup (because sometimes it pops _under_ other windows) then you just start getting silent failures. With absolutely NO indication in the UI that something is wrong. There is literally no way to find that out without looking directly into the TCC database.

TCC permissions are always evaluated by whether the parent process has the permission if it isn't being spawned by LaunchServices.

Reply on news.ycombinator.com