opentok-android-sdk-samples: Session.disconnect crash

Hi, in version 2.16.2 calling Session.disconnect() is throwing java.util.ConcurrentModificationException.

Pre-conditions:

  • We are using the SDK to create a video-conference between multiple users.
  • We have 3 (or more) users (different devices) connected to the conference.
  • In any device, call Session.disconnect()

App is crashing while SDK is calling clearPublishersAndSubscribers method

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 2
  • Comments: 17 (5 by maintainers)

Most upvoted comments

Hi,

A patch to fix it will be released in v2.16.3 soon.

Best, Marina

Going to close the issue due to inactivity, please reopen or report a new issue if you still have problems

We are also facing this same issue.

Exception: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.next(ArrayList.java:860) at com.opentok.android.v3.Session.clearPublishersAndSubscribers(Session.java:670) at com.opentok.android.v3.Session.disconnect(Session.java:319) at com.opentok.android.Session.disconnect(Session.java:903)

@robjperez Yes, but that version has different issues so we do not use it on production.

@janosvajda Same issue here, had an issue on the previous sdk, upgraded to 2.17 hopping that it would fix it. Ended up breaking other features…

@edwardbrosens I described the issue in my previous comment about what I experienced when I upgraded Tokbox SDK… I think @adrienrx reacted to my comment and he experienced the same what I did.

Same here, moving to 2.17 doesn’t help since it’s introducing new issues.

Hi, @robjperez I tried to upgrade our Android app twice but I failed. Because of losing video on the publisher’s side. I try to describe it a bit more detailed. So, when I tried to use 2.17 in the app (this is the subscriber) then the publisher did not see the video coming from the mobile. This publisher’s part of our system is in the browser (Chrome). And, this side uses OpenTok 2.16.6 JavaScript SDK.

So, this is why I have not done the upgrade of our Android app from com.opentok.android:opentok-android-sdk:2.16.4 to 2.17.

When I rolled back OpenTok Android SDK to 2.16.4 then everything worked perfectly again.