incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avidan Chen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-115) Pause/Resume events do not fire when locking/unlocking screen in ios < 5
Date Wed, 14 Mar 2012 20:18:40 GMT


Avidan Chen commented on CB-115:

Thanks for the explanation. It took me some time, but after I first encountered this issue
(was a couple of months ago) I eventually found out that applicationDidEnterBackground does
not fire in iOS 4 when locking the app. I overcome this issue by manually implementing the
resign and active events (I'm still using phonegap 1.2.0 which does not have these events).

However, I thought it would be best to create a consistent experience for JavaScript developers
who are not familiar with the details of iOS events. Wouldn't it be best to fire the pause/resume
events instead of resign/active? We would need some logic to make sure that pause/resume does
not fire twice in iOS 5, but it would make the behavior consistent.

What do you think?
> Pause/Resume events do not fire when locking/unlocking screen in ios < 5
> ------------------------------------------------------------------------
>                 Key: CB-115
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.2.0
>         Environment: iOS < 5
>            Reporter: Avidan Chen
>            Assignee: Shazron Abdullah
>              Labels: iOS4
>             Fix For: 1.6.0
> I have tested this in the iOS simulator (4.3.2) and an actual device running iOS 4.2.1.
When locking the screen with the power button and then unlocking it, in iOS 5, the pause and
resume events fire properly.
> However, in iOS 4, these events do not fire.
> Anyone else seen this? Is there any fix on the way?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message