

With App Sandbox, you can receive Apple events and respond to Apple events, but you cannot send Apple events to arbitrary apps. However, you cannot sandbox an assistive app such as a screen reader, and you cannot sandbox an app that controls another app.

With App Sandbox, you can and should enable your app for accessibility, as described in Accessibility Programming Guide for OS X. Use of accessibility APIs in assistive apps With App Sandbox, you cannot do work with the functions described in Authorization Services C Reference. The following app behaviors are incompatible with App Sandbox: Also, if you request a temporary exception, be sure to use the Review Notes field in iTunes Connect to explain why the exception is needed. Apple considers feature requests as it develops the macOS platform. If you choose to not sandbox your app now, or if you determine that you need a temporary exception entitlement, use Apple’s bug reporting system to let Apple know what’s not working for you. For example, if your app depends on hard-coded paths to locations in the user’s home directory, consider the advantages of using Cocoa and Core Foundation path-finding APIs, which use the sandbox container instead. If you need behavior in your app that App Sandbox does not allow, consider an alternative approach. Most macOS apps are fully compatible with App Sandbox. Where YourAppBundle.app should be replaced by the path to your app bundle.ĭetermine Whether Your App Is Suitable for Sandboxing Find -H YourAppBundle.app -print0 | xargs -0 file | grep "Mach-O.
