Opentok Stream not getting destroyed

[gourav-singhal]

We are performing a pre-call test as per the method described here.

But the connect and subscriber streams created during the pre-call test are not getting destroyed as soon as the session.disconnect() is called. Moreover, as soon as we move to the actual video call after recreating the same session, the older connection stream is again created then destroyed.

The above mentioned scenario is causing blank screen or unnecessary destroy calls. Please can you advise on this.

[vona-ben]

Hi @gourav-singhal

We have made some changes in our platform which may affect disconnect behaviour. We will keep you updated on any fix deployed. Could you please try to unpublish before calling session.disconnect ?

[gourav-singhal]

@vona-ben thanks for a quick response hoping for an early fix as this issue is impacting Live users for our apps.

Meanwhile we will try the proposed solution at our end.

[gourav-singhal]

@vona-ben we tried the solution shared by you "unpublish before calling session.disconnect" if we unpublish the stream the stream gets destroyed but if we instantaneously rejoin the session after unpublishing the stream. The stream may still persist for some time.

The same issue is also described here as well:

Issue: 685

[vona-ben]

@gourav-singhal Sorry for the delay. We will release a new version soon which should fix that issue. I will keep you updated

[gourav-singhal]

@vona-ben thanks for your reply hoping for an early release as we have many Live tickets which have come through regarding this.

[vona-ben]

@gourav-singhal we expected a release for the native SDK this week and a fix for the react native app in the following week. Also, we can disable the reconnection feature in the meantime which should be a temporary fix (but the user will not reconnect if switching from wifi to 4G for example). For this, you can contact our support team.

[gourav-singhal]

@vona-ben thanks for the update & quick fix will check same once released

[danhilton1]

@vona-ben I've also noticed this issue on iOS (Swift). Do you know if there's a fix coming for this too?

[gourav-singhal]

@vona-ben any update on this when can we expect the fix for this ?

[vona-ben]

Hi @gourav-singhal,
Could you confirm if it's fixed in version 2.26.0?

[kapilmishr]

@gourav-singhal Please check with the latest version of react-native and reach out to Vonage support (https://api.support.vonage.com/hc/en-us) in case you still face issues.