Hot answers tagged sandbox
Yes, any application placed in the Applications folder can provide QuickLook support. Sandboxing does not affect an application's ability to support QuickLook. Mac OS X looks inside applications for a QuickLook plug-ins folder. The specific folder is: MyApp.app/Contents/Library/QuickLook/ Support for Automator and Spotlight can also be provided using ...
lsboxd is part of the OS X Sandbox. It allows communication between sandboxed applications. lsboxd is in the Launch Services API. It is the Launch Services Sandbox Daemon, which governs what apps can launch apps in the OS X sandbox. You can peruse the App Sandbox Guide for more information about sandboxing. PDF: App Sandbox Design Guide
Yes, you can add a Quicklook Plugin to an application. For example, QuickNFO uses one: QuickNFO Mac App store page
Try this. using terms from application "Mail" on perform mail action with messages theMessages for rule theRule -- The folder to save the attachments in (must already exist) -- Save in a sub-folder based on the name of the rule in Mail set subFolder to name of theRule tell application "Finder" set ...
The App can have read/write access to a location if it gets your permission using an entitlement as part of the App Sandbox, in other words this is how its suppose to work. The App is code-signed and trusted, its asking your permission, in theory all should be good. As noted in the Mac Technology overview: App Sandbox Introduced in OS X v10.7, App ...
Without recoding the app the meet Apple's guidelines, you will have to rely on selling your software outside the MAS. Plain and simple I'm afraid. There is no way around Apple's guidelines. They are written for a reason; to protect users from having apps install malicious components or components that may damage their systems, to promoting an exceptional ...
You're not seeing it correctly. Sandboxing doesn't bypass file permissions. If you don't have write access to a file then having the file-write entitlement won't give you write access to the file. Likewise the NSOpen/NSSave dialogs can't access anything they can't access with sandboxing off.
Of course this is possible - iOS sandboxes all applications by default and runs on the same Darwin core as OS X. Apple hasn't chosen to implement this on OS X, so you would have a lot of engineering work to bolt this extra security on top of OS X. In the short run, it might be easier to virtualize the OS if you only need to sandbox one or two applications.
Seems a simple restart into safe mode can fix this. https://www.princeton.edu/~jcjb/docs/osx_error_fix/
I ended up replacing TextEdit's code signature with an ad-hoc signature: sudo codesign -f -s - /Applications/TextEdit.app/ It disables sandboxing, so for example the preference files are in ~/Library/Preferences/ instead of the sandbox container. Edit: The dialogs returned after I reinstalled OS X, and now I'm getting errors like this for codesign -f -s ...
Try repairing the user permissions. http://www.ernieflores.net/mac-os-x-10-7-lion/repair-user-permissions-in-mac-os-x-lion/ In Lion, there is an additional Repair Permissions application utility hidden away. This tool is located inside boot Repair Utilities. Here’s how to access it. Restart Lion and hold down the Command and R keys. You ...
Only top voted, non community-wiki answers of a minimum length are eligible