I am packaging a few apps for macOS with code signing and notarization, but cannot access locations such as ~/Desktop with an operation not permitted error. I believe this is due to the fact that I have executable loader scripts in front of the binaries and the permission not being requested thru the normal way when finally executing the binaries. Running the loader thru Terminal results in Terminal.app requesting permissions to use ~/Desktop, and the application working normally. The double-click launch seems broken. Works fine in Mojave, but Catalina is enforcing something, I'm not sure what needs to be accomplished to allow normal file access. I've tried entitlements, but it didn't change the behavior. There's no need to sandbox as they are not for the app store. I've tried signing both items before the app but no result. Full Disk Access doesn't work except with the Terminal launch method.
Catalina: executable launcher script not passing permissions to second binary in Contents/MacOS?
Update. I have set up inherited security entitlement and added the interpreter from my script’s shebang to full Disk Access in security. Seems to work so far.
Hey @Benitoite,
could please share how it works for you. I have the same issue that need to share permissions with other excutables inside the same bundle
all thanks