Closed GoogleCodeExporter closed 8 years ago
Also, it's possible that this is the result of a ban.
Bottom line, we need to recover from this and not lock up like frigid bitch.
Original comment by darkimp...@gmail.com
on 19 Feb 2012 at 9:56
Original comment by darkimp...@gmail.com
on 20 Feb 2012 at 3:20
It looks like this is partially fixed as a side effect of another fix. However,
it still leaves the conversation in an inconsistent state. This means that it
looks like the 404ed stranger is still there, but the buttons and text box that
target that Stranger are unresponsive.
Current work around is to end the current conversation and start a new one. I'm
not sure if this will work if BOTH strangers are 404ed.
Original comment by darkimp...@gmail.com
on 20 Feb 2012 at 3:51
I haven't seen this in a while. If it does ever crop up again, a better work
around is to swap out the unresponsive stranger.
I will be adding logic to the application to handle a 404 in any event.
Original comment by darkimp...@gmail.com
on 20 Mar 2012 at 2:34
In every instance of this 404 problem, the offending stranger is connected
through chatserv. None of the other omegle servers have manifested this
behavior.
Original comment by darkimp...@gmail.com
on 2 Apr 2012 at 9:04
Original comment by darkimp...@gmail.com
on 3 Apr 2012 at 7:19
We now offer to disconnect the stranger if there is an error delivering the
message.
Original comment by darkimp...@gmail.com
on 3 Apr 2012 at 7:29
Original issue reported on code.google.com by
darkimp...@gmail.com
on 19 Feb 2012 at 9:48Attachments: