“We are unable to process your request”

on my iphone 6 im experiencing around 5 min. waits to start and once it does it will freeze on a random app and then ill have to go through the whole restart process again.

Looking at that code, I would suspect the data is nil error is coming from some other place, not from your NSURLSession completion block. If you are positive that's where the crash is, then if error is nil and data is nil, there must be an error HTTP response. Perhaps you're using the iOS 9 SDK and are getting tripped up by App Tranport Security. I do think you need to code more defensively there (check if data is nil, and check the HTTP response code).Anyway here's one big thing that won't work with that code: NSURLSession is an asynchronous API. The completion block has not yet been called (most likely the request hasn't even gone out) by the time you hit that code that's attempting to parse the result. It's like you asked your roommate to go to the store and get some beer and put it in the fridge, then immediately went to the fridge and tried to pour out a beer. It's just not there yet. You need to defer all that parsing stuff until after the result comes in (i.e. put it in a separate method and c

Good work. You just need to upload the new binary from Xcode, then after the build has finished processing (usually just a few minutes) go to the new app version in iTunes Connect, select the new binary you just uploaded, save and Submit for Review again. Unfortunately a new binary always means a whole new review cycle (they don't know what else you may have changed).

There's no API on iOS that will run your app code at any specific schedule in the background. It sounds like you've considered all the options. I think you'll have to submit a feature request describing your use case and hope for the best in a future iOS version.I suspect the problem with any such API is that some developers would abuse the heck out of it, running continuously in the background and destroying battery life. And of course Apple would get blamed. But if they could figure a way to prevent abuse somehow, it certainly would be useful for many cases.

Not part of the sim, but what about using QuickTime Player? It has a feature to record just part of the screen. Then use HandBrake to process, etc.◅▻

To really get an idea of how creating a clock using for example CMAudioClockCreate (on iOS) is useful when assigned to an AVPlayer masterClock and used with the method setRate: time: atHostTime: when syncing with user generated audio, it's recommended that you watch the WWDC presentation from 2012 called Real-Time Media Effects and Processing during Playback. Starting at 11 minutes into the presentation the subject Syncronizing Video to Custom Audio is discussed in depth. However, you'll probably want to start at the beginning to experience an excellent explanation of Time and CMTime and clocks in general.You'll find this presentation super helpful and I'm sure it will clear up some of the hazy bits.https://developer.apple.com/videos/wwdc/2012/#517

56 seconds sounds awfully excessive for that amount of data.I would run the requests through a debugging proxy such as Charles to verify exactly how long the network requests are taking.

I'm betting you did a bad thing in the process of conversion.