incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Swiernik (JIRA)" <>
Subject [jira] [Commented] (CB-1227) 'resume' event is not fired after WiFi is turned on/off when listening to 'online' or 'offline' events.
Date Tue, 14 Aug 2012 20:21:38 GMT


Michael Swiernik commented on CB-1227:

I think this is related to CB-541, here iOS has a quirk where you need to wrap stuff in timeouts
if they occur during the resume step.

That said, this is more than just a quirk with the resume event. In my testing, I had a different
place where an alert might fire if the app doesn't have a connection, and that would run as
the app was starting up and were not in the resume event. I had to get rid of that one as
well in order to make it work in this scenario.

Note that although CB-541 is listed as "fixed", there is no reference in the 2.0.0 documentation
about this quirk.
> 'resume' event is not fired after WiFi is turned on/off when listening to 'online' or
'offline' events.
> -------------------------------------------------------------------------------------------------------
>                 Key: CB-1227
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.9.0
>            Reporter: Gene Connolly
>            Assignee: Shazron Abdullah
> When listening for 'online' and 'offline' events in an iOS cordova app, if you  navigate
to the device's settings app, turn on or off the WiFi (toggle), when you return to the cordova
app it will be frozen.
> Notes: If you navigate away from the app again and return it will respond. If you are
only listening to 'online' then the issue will only occur when you turn the WiFi for a device
on. Opposite applies for 'offline'.
> This issue is best demonstrated by a simple app that sends notifications on 'online'
'offline' and 'resume'.

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