-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App not responding or crashing after unmounting OTSession + OTSubscriber #366
Comments
I think this is related to the issue #357 |
I believe it's indeed a SDK-related issue. At the moment I have to downgrade the OpenTok SDK to 2.15.3 as a workaround. The view can unmount without freezing now, but there's still a noticeable delay time until the view is completely unmounted. |
We have 2.15.3 and we are facing Android stuck issue. |
Some progress on this? |
We released today Android SDK |
there are no any versions on android/build.gradle in "react-native": "0.61.5", and on Ios I using 2.16.3 and I getting an error : my version of OT is "opentok-react-native": "^0.12.1", |
in your opentok/opentok-react-native/android/build.gradle can you change it to 2.16.3 now it like this dependencies { |
in branch master, it set as 2.16.1 |
Anyway with 2.16.3 version application not responding after calling this function OT.disconnectSession() |
Same problem here: React Native version: 0.59.5 Freezes and crashes the app on unmounting the OTSession component whenever there's a subscriber to it. Downgrading the OpenTok Android SDK version: 2.15.3 also causes this problem so the workaround isn't working for me. Logcat when app crashes: A/libc: FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x77077a3e98) With: React Native version: 0.59.5 Throws an error for OTSession connect expecting 3 arguments and instead receiving 2. I really need to fix it so I can give the app to my client and publish it already, any help would be really appreciated. |
@enricop89 any updates? |
@QuevedoIB that error is because you're using an old version of the opentok-react-native. The current one is 0.12.1. Can you please test updating the library? |
Can you please test the branch 0.12.2? If you see it working as expected I'll push it ASAP. |
current version 0.12.1 if you released 12.2 so you need to update master branch! |
Now it's released. Please test it again and let us know. Thanks. |
not app responding after disconnectSession() but now this error appears: OTSessionManager.disconnectSession was called with 1 arguments but expects 2 arguments. If you haven't changed this method yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away. |
Please try to reinstall the library (removing node_modules and then a npm install) |
The same issue in the basic sample app |
React Native version: 0.59.5 On unmounting session throws a Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x30342d6363633c The tombstone in android logcat is: I've been struggling for days, any help would be appreciated! |
any improvements on this ? |
@ggoldens Any updates? |
We're not able to reproduce it. If you are able to reproduce it on the basic sample app, could you please share your App.js file, and provide more info about the device you're testing? |
Hey guys, can you please let us know if you are able to reproduce it? |
I am facing same issue |
any updated on #84? |
my problem was that I used disconnectSession without arguments this work for me >>>> |
Thanks for the issue, can you check out the latest version of the library, and if your issue has not been resolved please reopen/create a new issue. |
Bug Report
Hi everyone!
I'm building a live-streaming app, with 2 different scenes for Publisher and Subscriber. The Publisher scene has OTSession and OTPublisher. The Subscriber scene has OTSession and OTSubsciber.
The Publisher scene disconnects from the session and unmounts normally, but the Subscriber scene will regularly cause the app to hang (or sometime crash) during unmounting.
Current bug behavior
App regularly not responding or crashes after unmounting a scene with OTSession & OTSubscriber.
Sometimes the scene will unmount fine, but only after a long delay.
Steps to reproduce
What is the expected correct behavior?
The Subscriber scene should unmount without any issue.
I've been pulling my hair out for the last 3 days trying to find a way to work around this but still in vain. I hope someone can point me in the right direction. I'd really appreciate it!
The text was updated successfully, but these errors were encountered: