[BUG][Mobile app Android] Stuck in 'Chat already closed. Please start a new chat'

[ear-dev]

If I let the session timeout on the android mobile app, then I get a message in the space where the composer is that says: 'Chat already closed. Please start a new chat'

However there is no way to start a new chat. No button to push, and navigating away from the widget back into the app, and then back again does not help. Even if I log out of the app, and back in, I'm still stuck. I think I have to delete all app data to get back to a state where I can use the chat again.

[ear-dev]

@bhardwajaditya this seems like a bad bug to me.... we'll want to prioritize this next, after the character dropping bug. Thanks.

[ear-dev]

@bhardwajaditya I figured out how to reproduce this issue on mobile.

• Open a chat in the mobile app
• Put the app in the background, without closing the chat
• let the chat timeout, or close it on the RC server
• Navigate back to the app and try to chat.

What happens is that the chat looks like it is open... i.e. the composer is available to type into, but the 'X' is no longer visible. If I type into the composer I get that "Chat already closed. Please start a new chat" message in a banner which has now replaced the composer.

When in this state, there is no way at all to get out of it except to delete all the app data on the myViasat mobile app.

Can we look at this one next please?

Perhaps the bug is just that the 'X' has disappeared, because if it were still visible I might be able to close this chat on the app side and start over.

[ear-dev]

Design: When the user navigates away from the webview in mobile, back into the app, and then later comes back to the chat, we want to reload the session every time.

• if the room is still open it will just reload the room.
• if the room has been closed, it will start a new session.
  ISSUE: this fix requires changes in the android app.

Alternative Design: Monitor specifically for that "Chat already closed. Please start a new chat" message (502 response code) an if we see it in livechat widget code, redirect the visitor to the 'new chat' page.

• Mobile only solution - redirect the visitor to the new chat page.
• What about this situation in webapp? how to handle? maybe just not handle this....