Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Crash-permittedBackgroundDuration

Hi All,

Layout: Tabs

Scenario: Transition from one window to another. It is not creating the window and displays a blank screen. When I checked the device log, it says the following:

Application Specific Information:
"TestApp" has active assertions beyond permitted time:
{(
<SBProcessAssertion: 0x7376970> identifier: Suspending process: TestApp[310] permittedBackgroundDuration: 10.000000 reason: suspend owner pid:28 preventSuspend preventThrottleDownCPU preventThrottleDownUI
)}

I just have a simple window with two tableview rows and a background image. In the table view click event, I'm using the current location.

Please advise.

Thanks,

Sravan

— asked September 1st 2010 by Sravan Vinjamuri
  • crash
  • iphone
  • permittedbackgroundduration
0 Comments

8 Answers

  • Accepted Answer

    Yes, it seems to be happening because of the analytics. When i was testing for network status by turning on AIRPLANE mode, my app showed a "no-network" pop-up. But when i close the app and try to open it again, I could see a crash report with the same exception and the app could not load after the default splash screen.

    When i turned analytics off, I no longer had this kind of crash reports. Thanks for finding this out Sravan!

    — answered October 7th 2010 by Karthika Podury
    permalink
    0 Comments
  • Can someone please explain why this happens and how to avoid this?

    Thanks,

    Sravan

    — answered September 1st 2010 by Sravan Vinjamuri
    permalink
    0 Comments
  • bump. I'm getting the same thing at times in my app. SDK 1.4.1.1

    — answered September 24th 2010 by Robby Dermody
    permalink
    0 Comments
  • I too am seeing this with SDK 1.4.1.1, on iOS 4.1. However, it seems that it is possible that this is when you do a "Run on Device" from Titanium Developer, and even though you'd "quit" the app on your phone, it was still actually running (because of Fast App Switching), so it gets aborted when the new version of your app gets installed. That's just a theory, but it seems to happen that way for me. I just watched that happen. I had had my app running on a phone via Run on Device, had quit the app by pressing the home button. Then, I went and did another Run on Device with a new build, and voila, right after it got installed I see a new crash log pop up in Xcode's Organizer for that phone/device, and with this same message.

    — answered September 24th 2010 by Christopher Bailey
    permalink
    0 Comments
  • Interesting. In my case, I have UIApplicationExitsOnSuspend set in my Info.plist, so my app should be fully closing when I press the home button. I'll look into this a bit more…

    — answered September 25th 2010 by Robby Dermody
    permalink
    0 Comments
  • I also have the UIApplicationExitsOnSuspend set in info.plist; however, the device log contains crash reports saying "AppName has active assertions beyond permitted time …..".

    Any update on this issue?

    Thanks,

    — answered September 29th 2010 by Sravan Vinjamuri
    permalink
    0 Comments
  • Additional Info: Its not happening when I set UIApplicationExitsOnSuspend property set to false.

    Is it a serious issue? I could see a lot of crash reports saying the same. Whenever I call openUrl or press home button I guess this is happening.

    Please advise.

    Thanks,

    Its been about 5 weeks I since I posted this. Still unable to get any help. Could anyone give me the details about the error, how to avoid this etc.

    — answered October 3rd 2010 by Sravan Vinjamuri
    permalink
    0 Comments
  • Atlast, I was able to figure out the root cause of this exception. It was the analytics. When you exit the application, it still tries to send some information I guess, and that is the reason why we are getting the exception.

    By making <analytics> to false in tiapp.xml resolved the issue.

    — answered October 7th 2010 by Sravan Vinjamuri
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.