Mac Catalina Permissions Issue

Support for macOS users and the Mac App Store package
Post Reply
leejk
Posts: 30
Joined: 03 Oct 2015, 04:18

Mac Catalina Permissions Issue

Post by leejk »

Hi,

Using the Mac App Store version has been working fine until I upgraded to Catalina. Whenever I use FileBot now to rename TV Shows, I get a permissions error like

Code: Select all

"FileSystemException: /Volumes/video1/recordings/Arrow.S08E01.mkv -> /mnt/distation/video1/TV/Arrow/Season 8/Arrow - S08E01 - Starling City.mkv: Operation not permitted"
. However I can write in that location just fine. Is there just a compatibility issue with FileBot and the new OS?
User avatar
rednoah
The Source
Posts: 19156
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Mac Catalina Permissions Issue

Post by rednoah »

macOS sandboxes apps, which means they don't share your permissions, and can do a lot less than you can, and they especially can't access system folders (any custom folder that you create in / is a system folder, since / is reserved for system folders).

:idea: I've read that Catalina makes / file system root read-only so even root can't create /mnt for that matter. So in this case, it's not a compatibility issue between FileBot and Catalina, but a compatibility issue between how you do things and Catalina. :lol:

:arrow: Presumably, you can only use your $HOME for local files, and /Volumes/<share> for remote files, just like with Ubuntu SNAP confinement.
:idea: Please read the FAQ and How to Request Help.
leejk
Posts: 30
Joined: 03 Oct 2015, 04:18

Re: Mac Catalina Permissions Issue

Post by leejk »

hmm... true I've read similar. /mnt is a place I've setup via automount to connect to my NAS. But even in terminal these locations are writable. And as mentioned they are writable in Finder. As a test I used Excel to save a workbook in this location; worked fine.
User avatar
rednoah
The Source
Posts: 19156
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Mac Catalina Permissions Issue

Post by rednoah »

Excel is not a Mac App Store application, so it's not sandboxed, so macOS is enforcing access restrictions not just on the file system layer, but also on the application layer (for sandboxed applications). That's entirely reasonable. SNAP does the same.

Just use /home or /Volumes like everyone else, or argue with Apple. The choice is yours.
:idea: Please read the FAQ and How to Request Help.
Post Reply