 |
| (Credit: Sandbox Developers, CA) |
Are you the the kind of person who will always irk your moods for a day started badly when working behind your Mac just because a usual application isn't offering the right access authentication as directed? well, it's time to say good-bye to that. At times applications you like most will not give you the best when opening, closing or saving vital documents either. Here's a problem i found of which am pretty sure many of you have troubleshooted it in a way that doesn't suggest. At time OS X users may face problems such as a program not allowing you to save relevant documents thus prompting you a critical message that quotes "You may not have permission to access a file you are trying to open" or other users may as well find themselves unable to save what they see is important for future reference from their point of edit.
Presumably, this reveals a lot than what the read/user access may tell when it comes to issues concerning sandbox system. Normally whatever program a user works with, traces of batch files are directly mirrored to a system folder named "User". Programs like TextEdit when launched points all end-results to the final sandbox operation folder where it's finally saved. Perhaps, a portion of work (On TextEdit) may at times not save your ongoing operation which may later mean an option of loosing all unsaved data. What does it mean? all your root access folder namely "user" may also be exhibiting same problem as seen on sandbox's source folder.
How users troubleshoot sandbox problems according to my research.
- Cases of sandbox errors may appear minor but when tacked badly may carry with it consequences. Errors that consecutively prompts during a saving order are much less risky than prompts shown during or after a critical update. Problems may build when such troubleshooting operations are done as follows:
- Attempting a fresh roll back to restore your machine on a previous or earlier state: - This will rather refresh the OS X execution layer but not rectify issues concerning the sandbox as all OS X version except Snow White Leopard v10.1 that will evade this, reason being the sandbox system supported is different from a domain that apple changed when coming up with Mountain lion v10.8. What happens is that the operating system assumes adjustments on programs but doesn't change the entire log as users expect.
- Attempting to clear cache via a console environment: - Again that will not buy you proper results as all consoles both from Linux & OS X platform perform legitimate functions that gets to avoid altering programs that reside in the sandbox folder. The definite reason behind it is, when coming up with lion especially v10.8.8 (an update seen from 10.8) developers evaded the adjustment-act on sandbox alteration by patching an update which restricted users from modifying viable extensions ie (com.apple.xxx extensions). This was to protect all applications within the sandbox folder -- Clearing cache won't help, maybe on v10.1 Leopard users.
The way forward.
- According to Scott Forstall, (Former senior vice president of iOS software) sees to it that every strong chain has it's weakest point - There's an option to fall upon if after-all data is vital for you. Lets try troubleshooting the sand-boxing errors:
{Open the Console program and search for "sandboxd," which is the daemon process (or "server") in the system that manages the sandboxing routines that programs like TextEdit interface with. With this search, you should be able to see a reference to the affected program along with any associated messages, such as the sandbox daemon denying access to a requested file. With Console open, you can try to use your application again and see if similar messages show up.}
or
 |
| Container folder as navigated on OS X |
{You can Go menu in the Finder (hold the Option key if the Library is missing), and then opening the Containers folder. In here you will see each sandboxed application's container named by its domain (e.g., "com.apple.TextEdit" for TextEdit), so locate the one for your program and move it to the desktop. Then relaunch the program and see if the problems go away}
Caution!- Do not be too fast in discarding the Sandbox container as this will still be holding your documents. Copy all that to a different physical location -- i prefer the desktop as this doesn't mimic extension from the sandbox cache.
_________________________________________________________________________________
Have Questions? Comments? Other Fix? Post them below
