Log in

[mjtitus]

There has been previous discussion about OpenTok sessions being terminated when the app moves to the background. This can happen not just when a user hits the home key, but also if there is a (push) notification alert (which triggers appWillResignActive). How are people handling this in your apps? Do you consider the chat session "terminated" and require the user to initiate a new chat? Or do you try reconnect to the session when the app returns to the foreground as quickly as possible?

We're trying to do the latter, but it can sometimes take several seconds to reconnect, which is not a seamless user experience. Any tips? Any chance of keeping the OpenTok connection open while in the background? Thanks!

[charley]

Due to technical constraints, we were forced to setup the OTSession to issue a disconnect on itself when the application enters background. The issue is that a backgrounded app cannot capture camera frames, and as soon as media starts to stall out, the connection is pruned server-side. We've looked at an implementation for going audio-only on background, but nothing has gone far past the prototyping phase. It's still a largely unanswered question for us, and I know it's something we want to tackle.