{"id":32670,"date":"2021-06-01T17:02:02","date_gmt":"2021-06-01T21:02:02","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=32670"},"modified":"2021-06-02T16:47:19","modified_gmt":"2021-06-02T20:47:19","slug":"macos-11-4-breaks-full-disk-access-for-helper-tools","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/06\/01\/macos-11-4-breaks-full-disk-access-for-helper-tools\/","title":{"rendered":"macOS 11.4 Breaks Full Disk Access for Helper Tools"},"content":{"rendered":"

Jerry Krinock<\/a>:<\/p>\n

\n

I have been going through hell trying to maintain Full Disk Access for my apps’ background agents. I think something has changed with Full Disk Access[…]<\/p>\n

[…]<\/p>\n

Before Full Disk Access became a thing in macOS 10.15, my apps’ background agent was a command-line tool, shipped within my apps’ bundle, and launched intermittently by launchd tasks. Testing in early betas of 10.15, I could not find any way for a command-line tool to get Full Disk Access. (This may have been fixed in later versions.) Copying the design I saw in another app (Arq Backup) which had a working background agent, I spent several months replacing my command line tool with a Service Management Login Item which runs constantly.<\/p>\n<\/blockquote>\n\n

webjib:<\/p>\n

Before updating to 11.4, if user granted Full Disk Access to the main app, the Helper Tool got Full Disk Access too, as stated here<\/a> by eskimo.<\/p>\n

But now, it’s not working anymore. The Helper Tool doe not inherit from the main app, either the Full Disk Access but also the authorisations like Automation for Finder.<\/p><\/blockquote>\n\n

It remains frustrating how it’s mostly not documented how TCC is suppposed to work. And how, even when you figure it out, it seems to randomly fail on certain Macs until macOS is reinstalled and\/or you disable SIP and delete the database.<\/p>\n\n

Previously:<\/p>\n