[
https://issues.apache.org/jira/browse/CB-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957912#comment-13957912
]
Ronald Jeremy edited comment on CB-2301 at 4/2/14 5:49 PM:
-----------------------------------------------------------
This issue should NOT be closed. I have been tearing my hair out because of
this. In my apps the websocket needs to stay connected even when the app is in
the Inactive and background states, so closing the socket on "pause" is not an
option.
I am using the socket.io 0.9.9 client, Cordova 3.4.0, and iOS 7.1 on an iPad
mini. Everything works great when the app is in active, inactive, and
background states. But when the app goes into and comes out of suspended state
(i.e. a few minutes after locking the screen and background stuff the app is
doing like getting gps coordinates is done), it crashes almost every time with
EXC_BAD_ACCESS.
If i don't have a socket open when the app goes into suspension = no crash.
And also it works fine on just a regular mobile safari page. So this bug
definitely does exist.
If there was an event like "app will be suspended" that would be a possible
workaround to close the socket then, but I don't believe such an event exists.
was (Author: ronaldjeremy):
This issue should NOT be closed. I have been tearing my hair out because of
this. In my apps the websocket needs to stay connected even when the app is in
the Inactive and background states, so closing the socket on "pause" is not an
option.
I am using the socket.io 0.9.9 client, Cordova 3.4.0, and iOS 7.1 on an iPad
mini. Everything works great when the app is in active, inactive, and
background states. But when the app goes into and comes out of suspended state
(i.e. a few minutes after locking the screen and background stuff the app is
doing like getting gps coordinates is done), it crashes almost every time with
EXC_BAD_ACCESS. If i don't have a socket open when the app goes into
suspension = no crash. And also it works fine on just a regular mobile safari
page. So this bug definitely does exist.
If there was an event like "app will be suspended" that would be a possible
workaround to close the socket then, but I don't believe such an event exists.
> EXC_BAD_ACCESS on resume/wake on iOS device
> -------------------------------------------
>
> Key: CB-2301
> URL: https://issues.apache.org/jira/browse/CB-2301
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 2.2.0
> Environment: iPhone 5 running iOS 6.0.2 and Phonegap 2.2.0. (Xcode
> 4.5.2 on Mountain Lion)
> Reporter: Ross Holdway
> Assignee: Shazron Abdullah
> Priority: Critical
> Labels: cordova, ios, phonegap
> Fix For: 2.5.0
>
> Attachments: Sample.zip, Screenshot.png
>
>
> I have implemented a websocket connection (using socket.io) within my app
> which it uses to communicate with the server. On locking and waking the
> device, it disconnects and reconnects correctly, but on leaving the device
> locked for 1 minute or longer when unlocking, the application will crash
> sometimes instantly, or sometimes after reconnecting with the server.
> If I do the same, but run my app within mobile Safari, it does not crash,
> leading me to believe this is an issue with Phonegap/Cordova.
> On app crash, within Xcode I get within WebThread -
> WebCore::ThreadTImers::sharedTimerFiredInternal() an EXC_BAD_ACCESS (code=1)
> error
> Screenshot of crash state in Xcode
> -http://pictat.com/i/2013/1/28/24904screenshot.jpg
> Hopefully someone will have an idea as to what could be causing this, or
> recommend some tests for me to run etc because I'm really clueless on how to
> proceed with fixing this!
> Many Thanks,
> Ross
--
This message was sent by Atlassian JIRA
(v6.2#6252)
