Update 2022/05/31: After upgrading to macOS 12.4, Apple’s terminal app does not need to set the “Full Disk Access” permission, but this problem still exists in third-party apps.
As a developer who takes data security very seriously, I have been using a dual redundant 5-bay Drobo DAS disk array as external data storage.
For convenience, I set up Drobo DAS directly as a backup volume for TimeMachine and TimeMachine sets up a dedicated folder named “Backups.backupdb” in it. I also created other folders in the root of this backup volume to save some other files, such as videos, source code repositories, large project files, etc.
Since my daily work covers various aspects such as graphic design, front-end interface, back-end services, AI analysis, video editing, etc., the technology stack and tools include NodeJS, FCP and others that generate a lot of fragmented files. Therefore, I am used to operating the project files on the Drobo disk array.
Everything was perfect, the performance and capacity of the Drobo made my work very smooth, but it all ended in macOS 12.3.1.
After a routine upgrade prompt on the macOS system, I upgraded from macOS 12.2.1 to macOS 12.3.1, and then I found that my productivity softwares such as TextMate, Visual Studio Code, Visual Studio for Mac, Unity, Unreal and others could not obtain access permission to the project files in Drobo.
Even when Apple’s built-in terminal application runs third-party commands such as yarn, npm, node, etc. to the these project files, it will also prompt that there is no access permission.
I googled for a long time and didn’t see any solution, and finally I found that I can only obtain the access permission of these project files normally by setting all these softwares to “Full Disk Access” in “System Preferences” ▸ “Security and Privacy” ▸ “Privacy”.
It’s ridiculous, inconvenient and dangerous. Maybe later version of macOS will fix it?
- @ 2022年5月5日 上午10:54