BT Sport app crashing after 10 minutes using Airplay

Nosferatu

14-09-2013

Hello all,

I assume I'm not the only one having this problem but I can't find anything in the forums or online.

I tried to watch the Man U. v. Palace game today using the BT Sport app on an iPad 2. I was using Airplay to an AppleTV so the screen on the iPad goes blank.

After ~10 minutes of working fine the AppleTV switches back to its home screen. If you unlock the iPad it's back on its home screen too and you have to restart the BT Sport app (which logs in again) and then pick the channel and tap watch again.

The app is generating crash log files that are backed up by iTunes.
They all contain this message:

Code:

BTSport[3238] has active assertions beyond permitted time: 
{(
    <BKProcessAssertion: 0x1d5611b0> identifier: UIKitBackgroundCompletionTask process: BTSport[3238] permittedBackgroundDuration: 600.000000 reason: finishTask owner pid:3238 preventSuspend  preventIdleSleep ,
    <BKProcessAssertion: 0x1d57a390> identifier: UIKitBackgroundCompletionTask process: BTSport[3238] permittedBackgroundDuration: 600.000000 reason: finishTask owner pid:3238 preventSuspend  preventIdleSleep ,
    <BKProcessAssertion: 0x1d561220> identifier: UIKitBackgroundCompletionTask process: BTSport[3238] permittedBackgroundDuration: 600.000000 reason: finishTask owner pid:3238 preventSuspend  preventIdleSleep ,
    <BKProcessAssertion: 0x1d55e210> identifier: UIKitBackgroundCompletionTask process: BTSport[3238] permittedBackgroundDuration: 600.000000 reason: finishTask owner pid:3238 preventSuspend  preventIdleSleep 
)}

I'm not an XCode expert but reading around the Internet suggests that the app is trying to make a call it shouldn't be after it has been running in the background for 10 minutes. The app is running in the foreground when the screen goes blank.

The app was updated today but the crash was happening before and the log files contain the same message.

I've submitted feedback with these details to BT Sport on their feedback page.

Is anyone else having this problem?

James

victorslot

15-09-2013

There was an update to the App a few days ago I believe. I haven't used it nice then. Used iPad 3 to ATV a couple of weeks ago for rugby on ESPN without any problems.

If I get the chance later will run a test and let you know.

victorslot

15-09-2013

Have just run tests on all three channels using iPad 3.1 and ATV via AirPlay all with the same result as you at about 11 to 12 minutes.

Will check other reports. Please report back with any reply you get from BT.

D_J

15-09-2013

Just registered to let you know

The problem is the app stops transmitting when the ipad locks, set this to never lock in general options think its called autolock from memory, I have been able to watch a couple of full matches on my Apple TV with no disconnects

prior to that I was air playing using mirroring but although it was not disconnecting it didnt fill the tv screen so I started messing around and found this, I'm sure it will be an easy fix for them to keep the ipad from locking while is using airplay but you can do this for now

victorslot

16-09-2013

Thanks DJ. This seems to be the solution for now but currently getting lots of pauses/stuttering so will run some tests when the connection is better.

Nosferatu

22-09-2013

BT Sport called me last week to follow up but I wasn't around, I'll try to get back in touch with them this week.

The timing of the problem doesn't match my lock settings. I have auto-lock after 2 minutes and passcode lock after 15 minutes (I can't set these longer or off because the iPad has a company profile installed). The problem occurs after 10 minutes, long after auto-lock has engaged and before a passcode is required (I don't need to use the passcode to unlock the iPad after the BT Sport app has crashed).

The problem has got much worse with iOS 7, the operating system now limits these calls from background apps to 3 minutes (180s) rather than 10 minutes (600s). The iOS 7 crash logs contain:

Code:

BTSport[881] has active assertions beyond permitted time: 
{(
    <BKProcessAssertion: 0x165bcaa0> identifier: Called by BTSport, from unknown method process: BTSport[881] permittedBackgroundDuration: 180.000000 reason: finishTask owner pid:881 preventSuspend  preventIdleSleep  preventSuspendOnSleep ,
    <BKProcessAssertion: 0x165d24a0> identifier: Called by BTSport, from unknown method process: BTSport[881] permittedBackgroundDuration: 180.000000 reason: finishTask owner pid:881 preventSuspend  preventIdleSleep  preventSuspendOnSleep ,
    <BKProcessAssertion: 0x166b5150> identifier: Called by BTSport, from unknown method process: BTSport[881] permittedBackgroundDuration: 180.000000 reason: finishTask owner pid:881 preventSuspend  preventIdleSleep  preventSuspendOnSleep ,
    <BKProcessAssertion: 0x16591df0> identifier: Called by BTSport, from unknown method process: BTSport[881] permittedBackgroundDuration: 180.000000 reason: finishTask owner pid:881 preventSuspend  preventIdleSleep  preventSuspendOnSleep ,
    <BKProcessAssertion: 0x165b95d0> identifier: Called by BTSport, from unknown method process: BTSport[881] permittedBackgroundDuration: 180.000000 reason: finishTask owner pid:881 preventSuspend  preventIdleSleep  preventSuspendOnSleep 
)}

I still don't know why it's classed as running in the background, maybe as soon as the screen goes off the foreground app becomes a background app.

James

Nosferatu

22-09-2013

I should note that the BBC iPlayer app happily plays over airplay long after the screen has turned off and the passcode lock has activated, so it is possible for an app to do it properly with the same iPad settings. It even displays a control on the lock screen allowing you to pause/play etc.