Another sandboxing issue

  • I'm getting this logged in the sandboxed version of my app:

    <app name>(4041) deny file-write-data /Users/<me>/Library/Autosave Information/Unsaved <app name> Document.<ext>

    This appears to be when Lion's autosaves my untitled document. Seriously? Lion's own features don't even know when to use the sandbox.

    Does this imply I need to add this location to my temporary exceptions? Would that not apply to every doc-based app that supports autosave/versions? Joined-up thinking!

    --Graham
  • On May 29, 2012, at 8:54 AM, Graham Cox wrote:

    > I'm getting this logged in the sandboxed version of my app:
    >
    > <app name>(4041) deny file-write-data /Users/<me>/Library/Autosave Information/Unsaved <app name> Document.<ext>
    >
    >
    > This appears to be when Lion's autosaves my untitled document. Seriously? Lion's own features don't even know when to use the sandbox.
    >
    >
    > Does this imply I need to add this location to my temporary exceptions? Would that not apply to every doc-based app that supports autosave/versions? Joined-up thinking!
    >
    > --Graham

    I believe I read something about that last week over in the good old dev forums. IIRC the poster believed the app worked ok, it just logged a load of rubbish like that to the logfile, does your app still actually work? Is it writing Autosaved documents to the sandbox or just not writing them at all? Either way around it's still a bug but it may or may not be critical.
  • On 29/05/2012, at 11:18 AM, Roland King wrote:

    > I believe I read something about that last week over in the good old dev forums. IIRC the poster believed the app worked ok, it just logged a load of rubbish like that to the logfile, does your app still actually work? Is it writing Autosaved documents to the sandbox or just not writing them at all? Either way around it's still a bug but it may or may not be critical.

    It does appear to work correctly despite this.

    I have added an entitlement exception that shuts it up. I do see lots of responses on the sandboxing forum from Apple saying that various things are known bugs, but of course it's not Apple that are going to cop the stick for them when users are exposed to them.

    --Graham
previous month may 2012 next month
MTWTFSS
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
Go to today