Re: recent applications list question

Sorry for the big delay here but I’m having trouble to get this to work. Should I be using LSRegisterURL or something else? > On 7 Sep 2015, at 5:54 PM, dangerwillrobinsondan...@gmail.com wrote: > > Launch Services definitely used to have functions for manipulating recent > items. > They mi

Re: Obj-C - your thoughts on hiding data members?

> On 26 Jan 2016, at 19:10, Jens Alfke wrote: > > >> On Jan 26, 2016, at 6:32 AM, Alex Zavatone > > wrote: >> >> Since we're all computery and programmy and stuff, couldn't we put together >> a little matrix of the type of variable and come up with several loose >> stand

Re: Obj-C - your thoughts on hiding data members?

> I'd suggest it's not necessary. What I like about member naming conventions > has to do with identifying their scope. In my personal programming style, I > name things with a single lower-case letter to make their scope known; that > makes it much easier to track down a variable and understand

Re: Obj-C - your thoughts on hiding data members?

>> >>> I'm going to step out on a limb and since Xcode has supported editing in >>> UTF-8 and 16, that we look into those character sets and pick some symbols >>> that accurately represent public, protected and private. >> >> Now you’re pulling our legs, right Alex? > > Yeah, I know. It's re

Re: App Transport Security exceptions App Store signed app

> Also, have you looked into setting up HTTPS on those servers instead of > working around its absence? Part of the reason Apple added ATS was to nudge > app developers to make their network connections more secure, which will > benefit users. It is basically a cost issue. It is expensive to set

Re: App Transport Security exceptions App Store signed app

> On 26 Jan 2016, at 9:55 pm, Trygve Inda wrote: > >> connection failed: (null) The resource could not be loaded because the App >> Transport Security policy requires the use of a secure connection. >> http://www.earthdeskcloudhost02.com/mosaic/free/clouds-2048.jpg > > I'm no App Transport Secur

Re: App Transport Security exceptions App Store signed app

On Tue, Jan 26, 2016 at 11:18 PM, Jens Alfke wrote: > I believe you’re using the wrong key. If you need non-SSL connections to > work, the key you want is NSAllowsArbitraryLoads. The key you’re using is > for situations where you make an SSL connection but the SSL server doesn’t > meet ATS’s secu

Re: Obj-C - your thoughts on hiding data members?

> On Jan 27, 2016, at 03:38, Dave wrote: > > >>> I'm going to step out on a limb and since Xcode has supported editing in UTF-8 and 16, that we look into those character sets and pick some symbols that accurately represent public, protected and private. >>> >>> Now you’re pul

Re: LGPL code in the Mac App Store?

> On Jan 26, 2016, at 10:59 PM, Pascal J. Bourguignon > wrote: > > Sorry, I thought the context was iOS (and therefore distribution thru the > AppStore). I still don’t see why you wouldn’t be able to submit an app to the store that contains LGPL code. For one thing, Apple’s reviewers have no

Re: LGPL code in the Mac App Store?

There are/were some restrictions on GPL, but even those often go through and only get removed in the instance of a dispute. I think there has been some redressing of specific language in the GPL to address the issues. LGPL should be fine though, and there is a fair amount go GPL code in AppStore

Re: LGPL code in the Mac App Store?

> On Jan 26, 2016, at 11:48 PM, Quincey Morris > wrote: > > It would be the end of the App Store if it were possible to strip the code > signature out of a downloaded app and then just run it. Hm, I hadn’t thought of this in terms of cracking DRM. (Though of course, all forms of DRM have bee

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 7:32 AM, Trygve Inda wrote: > > It is basically a cost issue. It is expensive to set up SSL certificates on > 8 different servers... It would cost us about $700/yr Sounds like you’re being overcharged. SSL on hosted domains used to be pricey (partly due to the CPU overhea

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 7:53 AM, Sixten Otto wrote: > > According the docs, it's also for the case where the connection needs to be > made over non-S HTTP: "With this key’s value set to YES >

Re: Obj-C - your thoughts on hiding data members?

> On Jan 27, 2016, at 4:38 AM, Dave wrote: > >>> I'm going to step out on a limb and since Xcode has supported editing in UTF-8 and 16, that we look into those character sets and pick some symbols that accurately represent public, protected and private. >>> >>> Now you’re pull

Re: App Transport Security exceptions App Store signed app

On Wed, Jan 27, 2016 at 10:29 AM, Jens Alfke wrote: > I believe that text refers to an *SSL* server "with no certificate, or a > self-signed, expired, or hostname-mismatched certificate”. There is a > _separate_ key that allows non-SSL connections. > Reading over the rest of the page, I'm fairly

Re: Obj-C - your thoughts on hiding data members?

> On Jan 27, 2016, at 11:49 AM, Carl Hoefs > wrote: > > If I can't make a punched card deck out of it, it ain't REAL source code. Would that be punched on 80 or 96 column cards ? -rags ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Plea

iOS app HTTPS handling differences on development vs. Ad-Hoc distributables

I hope this is the correct place to post this question. After fixing the code signing issue that plagued us yesterday, I just started testing the ad-hoc distributable of our iOS app. This app uses push notifications and https communication to an internal web service end point and upon launch re

Re: Obj-C - your thoughts on hiding data members?

On Jan 27, 2016, at 6:38 AM, Dave wrote: > >>> I'm going to step out on a limb and since Xcode has supported editing in UTF-8 and 16, that we look into those character sets and pick some symbols that accurately represent public, protected and private. >>> >>> Now you’re pullin

Re: Obj-C - your thoughts on hiding data members?

> On Jan 27, 2016, at 11:49, Alex Zavatone wrote: > > > On Jan 27, 2016, at 6:38 AM, Dave wrote: > >> > I'm going to step out on a limb and since Xcode has supported editing in > UTF-8 and 16, that we look into those character sets and pick some > symbols that accurately r

Re: App Transport Security exceptions App Store signed app

> >> On Jan 27, 2016, at 7:32 AM, Trygve Inda wrote: >> >> It is basically a cost issue. It is expensive to set up SSL certificates on >> 8 different servers... It would cost us about $700/yr > > Sounds like you’re being overcharged. SSL on hosted domains used to be pricey > (partly due to the

Re: Obj-C - your thoughts on hiding data members?

> On Jan 27, 2016, at 03:30 , Dave wrote: > >> I would strongly urge that anyone prefixing ivars use this convention, for >> consistency. Additionally, I find that the underscore adds less visual >> clutter than a letter like “m”. Your brain doesn’t see it as a letter, so it >> doesn’t get in

Re: App Transport Security exceptions App Store signed app

On Tue, 26 Jan 2016 22:18:45 -0800, Jens Alfke said: >Also, have you looked into setting up HTTPS on those servers instead of >working around its absence? Part of the reason Apple added ATS was to >nudge app developers to make their network connections more secure, >which will benefit users. Some

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 12:55 AM, Trygve Inda wrote: > > Calls to http on my domain (xericdesign.com) work. Calls via http to my > other domain (earthdeskcloudhost02.com) do not work. .. you (and others) may find this option on the nscurl command nscurl --ats-diagnostics --verbose http://www

Re: App Transport Security exceptions App Store signed app

Here’s another discussion on nscurl that might help from Quinn at Apple DTS with a little more info. Thanks for the tip, Gavin. https://forums.developer.apple.com/thread/14816 On Jan 27, 2016, at 7:02 PM, Gavin Eadie wrote: >> On Jan 27, 2016, at 12:55 AM, Trygve Inda wrote: >> >> Calls t

Re: App Transport Security exceptions App Store signed app

> On Jan 27, 2016, at 7:14 PM, Alex Zavatone wrote: > > Here’s another discussion on nscurl that might help from Quinn at Apple DTS > with a little more info. Thanks for the tip, Gavin. .. Quinn’s a god! .. Here’s the CocoaHeads presentation I mentioned: https://www.dzombak.com/talks/2

Re: Obj-C - your thoughts on hiding data members?

On Jan 27, 2016, at 2:49 PM, Alex Zavatone wrote: > > On Jan 27, 2016, at 6:38 AM, Dave wrote: > >> > I'm going to step out on a limb and since Xcode has supported editing in > UTF-8 and 16, that we look into those character sets and pick some > symbols that accurately rep

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

I use -[NSData writeToURL:options:error] to write data to files in a location generally chosen by the user. That works fine. The default location is ~/Desktop, if the user fails to choose anything, or if the bookmark of the previously chosen location fails to resolve. However, when I try to wri

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

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

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

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

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

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

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

> 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 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 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 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