Hi,
I'm developing a sandboxed macOS application intended for distribution through the Mac App Store.
During TestFlight review, a build was rejected because it included the com.apple.security.temporary-exception.apple-events entitlement for interacting with Finder and Terminal.
The application only needs limited, user-initiated contextual information, such as the currently selected file or folder in Finder, or the working directory in Terminal.
I'm trying to understand the recommended, App Store-compliant approach rather than relying on temporary sandbox exceptions.
My questions are:
Is there an officially supported way for a sandboxed app to retrieve Finder's current selection when triggered by a global keyboard shortcut, without Apple Events?
Is accessing Terminal's current working directory supported under App Sandbox with explicit user consent?
Are Finder Sync extensions, Accessibility APIs, macOS Services, or other frameworks recommended for these use cases?
Are temporary Apple Events exceptions generally unsuitable for Mac App Store distribution, even when the interaction is explicitly initiated by the user?
I've already removed the entitlement from the current build, but I'd appreciate clarification on the recommended architecture for this type of integration.
Any guidance from Apple engineers or developers with similar experience would be appreciated.
Thanks!
2
0
95