
This means that, because it doesn’t even ask for permission, Emacs is simply forbidden from accessing certain files.Īpple did provide an escape hatch: Full Disk Access. Catalina now enforces these permissions at the filesystem APIs, as well.

Rather than using APIs to, say, access your contacts, you could just read the contact database via the filesystem. These prompts were displayed when using special APIs designated for those purposes.Īlas, there was an easy way to bypass these prompts. Here’s the gist of why this exists: In a previous version, macOS started displaying user prompts (similar to iOS) to grant application permission for accessing things like contacts, photos, location, etc. This is a ramification of the User Data Protection enhancements that were made in Catalina. Issue 1: I Couldn’t Access Certain FoldersĪfter the upgrade, Emacs was unable to access special folders, like the Documents folder.

Here’s a little insight into how I fixed them. Since the upgrade to macOS Catalina, I’ve had two serious annoyances with Emacs.
