incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric C (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-53) Bug when connect/disconnect while make ajax request (iOS)
Date Tue, 21 Feb 2012 20:26:48 GMT


Eric C commented on CB-53:

This is a big problem for the project I'm working on since the wifi is very spotty.

The project is written in Sencha Touch 1.1 and uses Ext.Ajax.request to make AJAX calls every
10 seconds.

The way I've reproduced this issue is:
- Open up the PhoneGap app on iOS device
- Walk out of range of wifi
- App crashes

Now, I'm unsure if the repetitive AJAX calls have anything to do with this, but looking at
the previous comment, it seems to be a factor.  I'll try and do a test with my AJAX requests
off and see if it crashes.  Also, in addition to testing on a physical iOS device, I tested
the app on the simulator by pulling out and putting back in the ethernet cable.  The simulator
fired off the online/offline events correctly and did not crash.
> Bug when connect/disconnect while make ajax request (iOS)
> ---------------------------------------------------------
>                 Key: CB-53
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>            Reporter: Shazron Abdullah
>            Priority: Minor
> reported at:
> by:
> Hi,
> I post it on start project because the link to iphone on wiki is wrong, but now i found
it searching on github.
> The problem is my app is make an ajax call every 1 second on my server and if i start
the app without internet connect and connect on wifi/3g the application is killed (fatal error).
Other situation is when im on my app connected and making ajax pooling and the connection
(wifi or 3g) is dropped, the application is killed too (fatal error).
> So, if you are making ajax call and your connection change state (connected/disconnected)
your app get a fatal error and close. :(

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