Re: Trying to understand a permissions failure when writing to ~/Desktop
Re: Trying to understand a permissions failure when writing to ~/Desktop
- Subject: Re: Trying to understand a permissions failure when writing to ~/Desktop
- From: Alex Zavatone <email@hidden>
- Date: Thu, 28 Jan 2016 13:15:57 -0500
On Jan 28, 2016, at 1:08 AM, Graham Cox wrote:
>
>> On 28 Jan 2016, at 4:36 PM, Graham Cox <email@hidden> 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 where it got that setting from (I’ve never set it), but it’s wrong. I deleted it and now my app seems to be happy to write where it wants to and doesn’t create a container.
>
> I’m supposing that the actual sandboxing entitlements are baked into the code signature, not just read from a resource file, and that’s where the system gets its info.
>
> So Alex, you were right ;)
Happy to help.
Thinking about how we solved this issue, I admit that I'm bit more spent than normal this week and only glazed over your "it's not a sandboxed app" part of your email, so yeah, bad form on my part.
But…
When looking at the situation, this screamed to me "well, that's just what Apple tells us a sandboxed app would do".
In this case, you reexamined what you assumed was true based on how the app was set up and well, damn. It was an untentionally sandboxed app.
As a lot of the reasons why we are here are to solve problems we are having in our Cocoa projects, what I like about this is it shows how we need to revisit our assumptions about what we think is true.
I had to do the same thing with our iOS dev account's distribution cert earlier this week. I had assumed that it was the most recent and therefore good. Since I do all the distribution here, I assumed they all were mine and therefore in my keychain with a private key. Well, this one wasn't.
Knowing when to revisit our assumptions and double check what we assume to be true can sure save time in a bunch of cases.
Now, back to making push notifications work in dev, adhoc and prod on multiple targets. Multiple certificates for everyone! Take 2, they're cheap.
> —Graham
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden