Crash on app resume about tiws

[allenhartwig]

I should add that this doesn't happen every time the app is resumed, nor have I been able to setup a reliable/consistent recreation of the crash, however, I have noticed it a handful of times on the resume event.

[allenhartwig]

Could potentially be related to this issue: facebookincubator/SocketRocket#62

[iamyellow]

Are you correctly closing the socket / opening it when pause / resume?
I'm very sorry, but recently I've decided to not develop my apps w/ Titanium and probably I won't update none of my modules...

[allenhartwig]

I think I fixed it. I had a setInterval running that was checking if the socket was connected, and if not, reconnecting it. However, I was referring to socket.socket.connected and I think the socket object was sometimes garbage collected in the background and had to be completely recreated.

Out of curiosity, what did you switch to for your app dev environment?

[iamyellow]

glad to read it's solved somehow.
after years with titanium, I don't like where AppC is focusing... plus the lack of important core updates, parity android <> ios, serious bugs, etc. honestly, i'm devolping faster in objc+java then titanium... since I got absolute control, performance and not those things I mentioned.

[cendrizzi]

This is disappointing to hear, but whatever works best I guess. I was a big fan of this particular module. Hope someone else can pick it up.