We have an AppleScript that clears up old files for a user. We went from a self distributed app using the Privledged Helper to now utilizing the Mac App Store. When a user updates to the new Mac Store App we have an optional function to save and run an Apple Script to remove the old helper plist files.
We use NSOpenPanel to ask a user to select the Apple Scripting directory which is assigned to our app and then using NSUserAppleScriptTask we are able to execute it. All while the user consents along the way.
In order to do this we need the entitlement com.apple.security.files.user-selected.read-write which is being denied by the App review team as they say its meant for PDF's, Images etc and NOT scripts.
If that entitlement is not meant for this situation, how are we able to get around this in a sandboxed app?
We use NSOpenPanel to ask a user to select the Apple Scripting directory which is assigned to our app and then using NSUserAppleScriptTask we are able to execute it. All while the user consents along the way.
In order to do this we need the entitlement com.apple.security.files.user-selected.read-write which is being denied by the App review team as they say its meant for PDF's, Images etc and NOT scripts.
If that entitlement is not meant for this situation, how are we able to get around this in a sandboxed app?