beginBackgroundTaskWithExpirationHandler doesn't expire - ios

Question

On connect i added this bit of code at the end of getting the user connected:
UIBackgroundTaskIdentifier myLongTask;
myLongTask = [[UIApplication sharedApplication]
beginBackgroundTaskWithExpirationHandler:^{
// If you're worried about exceeding 10 minutes, handle it here
}];
CFRunLoopRun();
[[UIApplication sharedApplication] endBackgroundTask:myLongTask];
I also set in build settings, application needs wifi. This is a basic client that uses a socket.
Before if i locked the iPad the internet died. Now i was expecting it to stay alive for 10 minutes after the iPad locks but for some reason it just stays on indefinitely so far. I've measured the internet being on over 30 minutes after i lock the phone and come back and unlock and my connection is still streaming chat.
I'm concerned this may not be legal app behavior for acceptance in app store though i did not set any special settings i was reading about that this is a VOIP app. I just used the beginBackgroundTaskWithExpirationHandler, and application requires internet. I'm also concerned about long term battery impact if indeed the application never really sleeps, though the server i'm connecting to would disconnect you if idle for 60 minutes so it would not stay connected indefinitely but still its a concern if this loop always runs even after a disconnect it could use battery. For example what if the user leaves the app and doesnt come back for over a week and the iPad is just sitting locked for a week would it use accelerated battery? My testing hasn't got that far yet as this is a new situation this morning that i have were internet wont turn off were before it shut the connection any time the screen locked.
Any suggestions? Anyone know why the app wont sleep after 10 minutes of a screen lock?
Mike

Answer 1

the os may kill you or it may not. the 10 minutes are more like a 'guideline' but the os may kill you earlier or later anyways.
but CFRunloopRun will run almost indevifinitly (well as long any source is attached or it is stopped). make sure it ends or you never end the bg task.
not forbidden but not cool!

Answer 2

This is a very strange way to setup a background task request. It is unusual to call CFRunLoopRun() manually this way as well. The fact that you do this on the main loop suggests that you're not using the standard UIApplicationMain() function. If not, then you may not be setting up the application correctly, and behaviors can be erratic. Have you tried using background tasks the normal way:
beginBackgroundTaskWithExpirationHandler:
Do the specific task you would like to run even if the program goes into the background
endBackgroundTask: when that task is done
The way you're doing it, endBackgroundTask: is likely never called.
EDIT: If your goal is to be allowed to run after going into the background for as long as the OS is willing to let you run (around 10 minutes), then call beginBackgroundTaskWithExpirationHandler: in applicationWillEnterBackground:. You don't need any special use of the runloop. You just need to tell the OS you'd like to keep going until it stops you.