eskimo

You should definitely file a bug about this. Please post your bug number, just for the record.If you can reliably reproduce the problem then it'd be great if you could attach a small test project to the bug. Also, if you can make sure it still happens on iOS 9 beta, that'd be grand.It sounds like something you're doing is tying nsurlsessiond up in knots such that it's got stuck in a tight loop. Eventually the watchdog kills it and things recover. However, given that your just dealing with a single upload task, it's not obvious how you managed to convince the daemon to get itself into this state. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I also got this issue on iOS 7.1.2. I still didn't find the exact issue, but it seems to be occuring when I'm queuing too much background downloads in too many different sessions. Can any one confirm there is a limitation?There's no concrete limit. In my experience, hundreds on tasks work just fine, things start to creak when you hit thousands of tasks, and tens of thousands of tasks would be a mistake.Having said that, NSURLSession's background sessions have improved a lot since the iOS 7 days. Have you been seeing the same sorts of problems on recent iOS 8 releases?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Alas, Radar will only let you see bugs that you've filed, and you didn't file these bugs. I include links like this just for the record; primarily it's so that Future Quinn™ can easily find the bugs if this discussion crops up again.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I'm not in a position to reverse engineer other developer's software on your behalf, or to comment on App Review policies, but my experience is that apps that are doing seemingly-impossible things fall into one of three categories:they're breaking the rules and App Review hasn't caught them yet (A)their marketing material is being economical with the truth (B)they are grandfathered in from a previous world (C)My guess is that point C applies in this case, although I'm not in a position to confirm that.Of course, you could do that easily:buy the appdownload itdump its entitlements$ codesign -d --entitlements :- /path/to/some.appI can say that there is no supported way to do Wi-Fi scanner from a sandboxed app, and that Mac App Store currently requires that all apps be sandboxed.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Sorry, I'm confused by you reply.You're asking how the sync is done, and I don't know how it's done. All I know is that it is done.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

tuncer had problems posting the crash log so they sent it to me. Here's the relevant snippet:0 libsystem_kernel.dylib __pthread_kill + 10 1 libsystem_pthread.dylib pthread_kill + 90 2 libsystem_c.dylib abort + 129 3 libmono.0.dylib mono_handle_native_sigsegv + 732 4 libmono.0.dylib sigabrt_signal_handler + 100 5 libsystem_platform.dylib _sigtramp + 26 6 libsystem_kernel.dylib mach_msg_trap + 10 7 libsystem_kernel.dylib mach_msg + 55 8 com.apple.CoreFoundation __CFRunLoopServiceMachPort + 212 9 com.apple.CoreFoundation __CFRunLoopRun + 1293 10 com.apple.CoreFoundation CFRunLoopRunSpecific + 296 11 com.apple.HIToolbox RunCurrentEventLoopInMode + 235 12 com.apple.HIToolbox ReceiveNextEventCommon + 432 13 com.apple.HIToolbox _BlockUntilNextEventMatchingListInModeWith… 14 com.apple.AppKit _DPSNextEvent + 945 15 com.apple.AppKit -[NSApplication _nextEventMatchingEventMas… 16 com.apple.AppKit -[NSApplication run] + 682 17 com.apple.AppKit NSApplicationMain + 1176 18 com.mpdigital.Infinifactory PlayerMain(int, char c

To start you need to symbolicate the crash log. For background on this, see TN2151 Understanding and Analyzing iOS Application Crash Reports. IMPORTANT The advice in the technote for how to symbolicate a log is incorrect (we're in the process of updating the technote right now). I recently posted up-to-date instructions in a different thread.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Hi eskimo,[[NSBundle mainBundle] preferredLocalizations]Only gives me one object and is en, has set the iPhone with the language in EN or PTThanks,JFontes

It sounds like you're crashing nsurlsessiond, the daemon responsible for handling NSURLSession background sessions. This is obviously not good, and also indicative of a bug in nsurlessiond because app code isn't supposed to be able to cause it to fail like this . If you import crash logs from the device (attach via USB, sync via iTunes, look in Xcode's Devices window), do you see any recent nsurlsessiond crash logs? If so, please post one. I tap on the startDownloads button many times (about 20-30 times to start about 2000-3000 downloads) and wait some seconds.So the total number of tasks you're starting is 40,000 to 90,000? Or 2,000 to 3,000? The latter should be fine; the former would definitely be asking for trouble.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I believe that CFNetworking is open source, so that could be a startJust FYI, there have been open source versions of CFNetwork in the past, but things have evolved a lot since then. You would not want to base any modern project on that code.[I was curious how old that code is, and it seems that it dates from the Mac OS X 10.4 'Tiger' timeframe, that is, about ten years ago.]Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

When I read that, I get the impression that if you only have en localization in your application bundle, then you're only going to get en back.Right, that's the way I interpret things as well.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

By (C) do you mean that the app was submitted when sandbox was not a requirements and now it is allowed to be updated and still be kept unsandboxed?I was talking in general terms, but in the specific case of the Mac App Store that certainly does occur. I don't work for App Review, so I can't tell you exactly how they interpret the 'major update' rule.I have bought the app [...]Well, if you have the app installed, it's trivial to see if it's sandboxed.If (A) is the case, is there a way to report/warn Apple Review that an app is doing malicious things and/or breaking the rules?If you believe that some app is not playing by the rules, you should get in touch with App Review.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

ATS applies to NSURLSession (and the now-legacy) NSURLConnection only.Of course, if you're using low-level APIs to implement your own TLS-based protocol, it'd be a good idea to require the same level of security as ATS provides. There is not currently a way to do that—you can reimplement ATS's algorithm, but there's no API that says 'do what ATS would do'—but that'd make a fine enhancement request.If you do file a bug, please post your bug number, just for the record.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

If you can reproduce the problem on iOS 9 beta, these crashes would make for a fine bug report. Please post your bug number, just for the record.As for the total started download, yes it's about 2000-5000 thousands downloadsAgain, I'm having trouble parsing your sentences. Read literally, 2000-5000 thousands means 2-5 million, which is clearly not OK. I presume you mean 2-5 thousand. That should be OK, but it's obviously not in your case. Are you sure you're not 'leaking' tasks in the background session. That's easy to do and would definitely reduce the number of tasks that you could successfully execute.But in our real app, we may have around 50 000+ files to downloads sometimes, but we wanted to throttle them over time (~100 concurrent downloads). Will it be an issue?50,000 tasks is definitely beyond the pale. Batching them into groups of 100 should be fine.I expect you'd be able to increase that group size and I recommend that you do because of the resume rate limiter.Of course the best solution here would

Is the total number of task an issue only only for concurrent downloads, or for the total number tasks than an application is launching over time?It should be the number you run concurrently.Keep in mind that the tasks you submit to the NSURLSession background session don't all hit the 'wire' simultaneously. The background daemon has its own queue that limits the number of concurrent requests that it will run on the network.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com