eskimo

So attaching debugger to osx apps is no longer possible?Did you watch the session I referenced? WWDC week is a bit of a blur for me, so I'd rather you get the answer first hand than rely on my sleep-deprived memories (-:Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Alas, you're really off in the weeds here.+[NSLocale currentLocale] returns the current locale, that is, the value set by Settings > General > Language & Region > Region Formats. It has nothing to do with the language that your app is running in. It's perfectly reasonable, and in fact quite common, for users in the field to have their locale and language set to 'conflicting' values. For example, a native English speaker living in France would have the language set to English but might choose to set the locale to French (so they get metric weights and measures, 24 time, and so on). The language that your app runs in is determined by the language setting, that is, Settings > General > Language & Region > Preferred Language Order. When the system runs your app it takes this list of languages (the preferred list) and matches it against the list of languages that your app is localised into (the app list). The first language in the preferred list that exists in the app list is the language

Rum wrote:And of cause, questions like your will get more answers if asked in more appropriate forums, like Core OS/NetworkingIndeed. I've just gone ahead and moved the thread there.bimal13 wrote:Like if user want to use Cellular than all data traffice will work with cellular only even if wifi is enaled.Are you trying to affect the traffic of just your app? Or all apps on the system?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

APPLE GET ON THE DOCS. WE'RE SUFFERING FROM GUESSWORK HERE!It's a little known fact that you can file bugs against the documentation in exactly the same way you file bugs against the system software. If you want your feedback to be heard by the folks who are responsible for addressing it, that's your best way forward.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

There is no supported way to get device model numbers (in Swift or not).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The problem here is that Cocoa conventions require the caller to first test the function result and then look at the returned NSError. There's an obvious interpretation of the first step for BOOL ( NO indicates an error) and pointers ( nil indicates an error) but not for integer types. In some contexts 0 indicates an error, in some it's -1, and in some it's NSNotFound. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I've moved you over to Core OS > Networking because the solution here won't be Swift specific.To start, there's no such thing as an Internet connection. There's two problems with this term:The Internet is not a homogenous thing. You can have access to some parts of it but not others.The Internet is packet based, not connection based, so asking about connections makes little sense. The N'th packet you send might make it through to the destination while the N+1'th does not, or vice versa.My general advice on this front is...Don't PreflightIf you need to make an Internet request, just make it. It's impossible for you to determine in advance whether a request will work or not and, even if you could, the answer could change immediately after you make that determination.Use Reachability Only For Failure and Retry GuidanceThe System Configuration framework reachability API can give you limited information about whether a connection to a particular host will work or not. This is not perfect—you can get both false

Hi eskimo,Thank you for your help.JFontes

Do you recommend me to use NSURLSessionUploadTask or another class?NSURLSessionUploadTaskWhat do I have to do to continue all these uploads in background?What do I have to do to continue all these uploads when app is not running?Dump all the uploads into an NSURLSession background session.For all of the first 3 points, do you recommend me to wrap NSURLSession objects in NSOperation ones in order to use an NSOperationQueue? Or iOS would use its own internal queue to properly handle NSURLSession objects?That's hard to say. In general I'm a big fan of NSOperation but it's a tricky fit for NSURLSession background sessions because of the way that the background session interacts with your app's lifecycle. Specifically, a common sequence is this:your app starts a bunch of background transfersthe user moves it into the backgroundthe system suspends your appthe transfers continue in the backgroundthe system terminates your appthe transfers continue in the backgroundthe transfers completethe system relaunches your app

See this thread on the old DevForums.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

is [NSURLCredentialStorage sharedCredentialStorage] thread safe?Yes.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I've moved your thread to Pre-Release > iOS 9 beta because this is more of a user-level question about the beta than a code-level question about networking.I don't know what's happen in your specific situation but my experience from previous beta releases is that Settings > General > Reset > Reset Network Settings cures a remarkable array of network problems.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Now the question is: what trusted certificate authority can purchase a such certicate from?AppleCare publish a list of trusted root certificates for each OS we ship. I don't think the iOS 9 one is out yet (which makes sense given that iOS 9 is not yet released) but the iOS 8 one is available here and my experience is that the list does not change radically from release to release.I can't make specific recommendations as to which of these CAs best meets your requirements; perhaps some other folks, with more experience in this area, will chime in.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Closing NSStream doesn't completely reset SSL connection as subsequent connection attempts have SSL SessionID from the previously closed session. Session ID only resets after process restart or after ~10 minutes.Indeed. This is expected behaviour as per QA1727 TLS Session Cache.It's weird that this is causing you problems: TLS session resume is a documented part of the TLS standard and AFAIK iOS implements it correctly. Certainly, if the iOS side of this were truly broken we'd know about it; it's used by millions of Safari users every day.Honestly, I suspect that this is a problem with your server. If the server is not prepared to resume a session it's supposed to ignore the client's proposed session ID and do the full handshake.If you can't fix the server then you can probably work around this on the client side, but IMO it'd be better to attempt a server-side fix first.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo

1) it appears that there is no graphical debugger like WinDBG on windowsCorrect.only gdb.We haven't used GDB for kernel debugging for a while. It's now done with LLDB.2) it looks like there is a tedious procedure to generate the debug symbols for the driver. Why doesn't the compiler generate the needed symbols?This is all much easier with modern versions of the system and LLDB.3) I've read that the target and debugger machine most both be running the same OS. Is this really true?No.It seems like you've been reading some out-of-date tutorials; as I mentioned, we haven't used GDB for kernel debugging for some years now (since 10.9 IIRC). Alas, our official documentation hasn't caught up with this change.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com