Re: Trying to understand a permissions failure when writing to ~/Desktop

> On 29 Jan 2016, at 4:51 AM, Lee Ann Rucker wrote: > > Now that this is all resolved, the next question - why default to Desktop > instead of Documents? I'd expect Documents, and I hate stuff that clutters up > Desktop - one of the first things I do on new installs is change the default > lo

Re: Trying to understand a permissions failure when writing to ~/Desktop

> On Jan 27, 2016, at 22:08, Graham Cox wrote: > > >> On 28 Jan 2016, at 4:36 PM, Graham Cox wrote: >> >> Why would the OS think an app was sandboxed > > > OK, I think I found the problem. In Build Settings->Code Signing, the “Code > Signing Entitlements” was set to a .entitlements file wh

Re: Trying to understand a permissions failure when writing to ~/Desktop

On Jan 28, 2016, at 1:08 AM, Graham Cox wrote: > >> On 28 Jan 2016, at 4:36 PM, Graham Cox wrote: >> >> Why would the OS think an app was sandboxed > > > OK, I think I found the problem. In Build Settings->Code Signing, the “Code > Signing Entitlements” was set to a .entitlements file which

RE: Trying to understand a permissions failure when writing to ~/Desktop

Now that this is all resolved, the next question - why default to Desktop instead of Documents? I'd expect Documents, and I hate stuff that clutters up Desktop - one of the first things I do on new installs is change the default location of screen captures to Pictures. __

Re: Trying to understand a permissions failure when writing to ~/Desktop

> On 28 Jan 2016, at 4:36 PM, Graham Cox wrote: > > Why would the OS think an app was sandboxed OK, I think I found the problem. In Build Settings->Code Signing, the “Code Signing Entitlements” was set to a .entitlements file which is actually nothing to do with this product. I don’t know wh

Re: Trying to understand a permissions failure when writing to ~/Desktop

On 28 Jan 2016, at 12:50, Dev Sqwarq wrote: > On 28 Jan 2016, at 12:36, Graham Cox > wrote: > > The app *has* been sandboxed in the past during development, so wondering if > there’s some info cached somewhere that needs clearing? Hey Graham Don’t know if a

Re: Trying to understand a permissions failure when writing to ~/Desktop

> On 28 Jan 2016, at 13:36, Graham Cox wrote: > > >> On 28 Jan 2016, at 3:07 PM, Kyle Sluder wrote: >> >> Any app on OS X can open documents from iCloud Drive—the user just has >> to navigate to iCloud Drive in Finder. >> > > > Well anyway, it was a red herring - has nothing to do with my

Re: Trying to understand a permissions failure when writing to ~/Desktop

> On 28 Jan 2016, at 3:07 PM, Kyle Sluder wrote: > > Any app on OS X can open documents from iCloud Drive—the user just has > to navigate to iCloud Drive in Finder. > Well anyway, it was a red herring - has nothing to do with my problem. Why would the OS think an app was sandboxed when it h

Re: Trying to understand a permissions failure when writing to ~/Desktop

On Wed, Jan 27, 2016, at 09:57 PM, Graham Cox wrote: > Well, the OS definitely believes the app is sandboxed. The full URL I get > for ~/Documents/ is in fact ~/Library/Containers//…. blah blah > > I did a clean build and changed the bundle ID as well as discarding the > container, but no, it just

Re: Trying to understand a permissions failure when writing to ~/Desktop

Well, the OS definitely believes the app is sandboxed. The full URL I get for ~/Documents/ is in fact ~/Library/Containers//…. blah blah I did a clean build and changed the bundle ID as well as discarding the container, but no, it just makes a new container with the new bundle ID. This is exasp

Re: Trying to understand a permissions failure when writing to ~/Desktop

have you checked your info.plist file just to be certain damned sure Xcode hasn’t slipped in something nasty whilst you weren’t looking? I’d actually look at the one in the app bundle you’re running because I’m paranoid like that. > On 28 Jan 2016, at 11:17, Graham Cox wrote: > > I did say

Re: Trying to understand a permissions failure when writing to ~/Desktop

I did say that, and the app definitely isn’t sandboxed (it’s running from Xcode also). However, I just noticed that I get this in the log when the app receives the error: 28/01/2016 12:26:35.124 PM sandboxd[127]: ([19475]) MyApp(19475) deny file-write-create /Users/grahamcox/Desktop/Untitled_0

Re: Trying to understand a permissions failure when writing to ~/Desktop

Sorry man. It’s been a long long day. On Jan 27, 2016, at 9:54 PM, Roland King wrote: > From the original mail > > "Note this isn’t a sandboxed app, so that shouldn’t come into it.” > > >> On 28 Jan 2016, at 10:51, Alex Zavatone wrote: >> >> According to the sandboxing docs, I recall that

Re: Trying to understand a permissions failure when writing to ~/Desktop

From the original mail "Note this isn’t a sandboxed app, so that shouldn’t come into it.” > On 28 Jan 2016, at 10:51, Alex Zavatone wrote: > > According to the sandboxing docs, I recall that for sandboxing, there are a > certain set of locations where you can save files to without requiring u

Re: Trying to understand a permissions failure when writing to ~/Desktop

According to the sandboxing docs, I recall that for sandboxing, there are a certain set of locations where you can save files to without requiring user permission. Your ~/Documents folder is one of them. IIRC, all other locations require user confirmation to save the files. Try saving to the d