March June, 2012, all Apps on the Mac Apple Store will be required to be Sandboxed, from the research I've found. Not Sandboxing isn't going to future-proof your app.
Second, I've found 3 strategies that you may consider:
- Look up the list of entitlements, and see if you can grant your app access via the Entitlements (Apple's way of allowing Apps special privileges to access key features they'lll need). Here's a walk-through via Apple's documentation on how you can stack-trace through which entitlements you're missing and might need.
- Submit a bug request to Apple on the specific feature you want access to. Who knows, they may actually update their codebase to allow you access.
- Consider selling the app as a product on an e-commerce site, and not selling on the Mac Apple Store. People can still buy and install your app on a regular website (as Versions, TextMate, and other wonderful applications have done before going on MAS), especially if your application does things that can't be found on the MAS.
If you look at the documentation, you'll find that it explicitly states you cannot sandbox an assistive app.
Here's an excerpt from their documentation on preparing an App for Sandbox:
Use of accessibility APIs in assistive apps
With App Sandbox, you can and should enable your app for accessibility, as described in Accessibility Overview. However, you cannot sandbox an assistive app such as a screen reader, and you cannot sandbox an app that controls another app.
Here's an excerpt from their documentation on Accesibility in Cocoa:
Note: With App Sandbox, you can and should enable your app for accessibility, as described in this document. However, you cannot sandbox an assistive app such as a screen reader, and you cannot sandbox an app that controls another app.
It sounds a bit like double-speak: you should enable your app to be Accessible however you cannot sandbox an assistant app...