jitsi-meet
jitsi-meet copied to clipboard
App Crashes Unexpectedly after joining a session
Description:
App Crashes Unexpectedly when joining a meeting
Steps to reproduce:
- Open the app
- Join session
- App Freezes and closes
Server information:
- Jitsi Meet version: Latest Stable on F-Droid
Client information:
- Browser / app version: 21.6.0
- Operating System - LineageOS 17.1
Please provide the adb logcat output.
i'm having same issue.
Can you provide the adb logcat output?
`2022-06-23 14:55:07.679 26765-27466/com..* E/AndroidRuntime: FATAL EXCEPTION: create_react_context
Process: com.., PID: 26765
java.lang.NoClassDefFoundError: com.facebook.react.jscexecutor.JSCExecutor
at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:29)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1112)
at java.lang.Thread.run(Thread.java:929)
Caused by: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so
SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/com..-dmhqxncifxjbXOcK7o_chQ==/lib/arm64 flags = 0]
SoSource 1: com.facebook.soloader.DirectApkSoSource[root = /data/app/com..-dmhqxncifxjbXOcK7o_chQ==/base.apk!/lib/arm64-v8a]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/com..-dmhqxncifxjbXOcK7o_chQ==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743)
at com.facebook.react.jscexecutor.JSCExecutor.loadLibrary(JSCExecutor.java:24)
at com.facebook.react.jscexecutor.JSCExecutor.
java.lang.NoClassDefFoundError: com.facebook.react.jscexecutor.JSCExecutor
at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:29)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1112)
at java.lang.Thread.run(Thread.java:929)
Caused by: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so
SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/com.*****.******-dmhqxncifxjbXOcK7o_chQ==/lib/arm64 flags = 0]
SoSource 1: com.facebook.soloader.DirectApkSoSource[root = /data/app/com.*****.******-dmhqxncifxjbXOcK7o_chQ==/base.apk!/lib/arm64-v8a]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/com.*****.******-dmhqxncifxjbXOcK7o_chQ==/lib/arm64
result: 0
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098)
at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743)
at com.facebook.react.jsce`
Hum, that's odd. What device are you using? Do you have the app installed on some kind of external storage?
Any chance you could test the play store version to check if you get the same result?
no, i don't have any external storage. I am using Google Pixel 4a as a testing device (Android 12).
Any chance you can test the play store version?
@saghul I am implementing the jitsi-meet android SDK into my react-native app using native bridge and getting this error. it would be helpful if you got any solution. Thank you.
Wait, so you are not running the app but using the SDK in a RN app? Sorry, those are 2 very very different things.
yes, so can you guide me for the implementing android SDK in RN app please? my requirement is make a video call using jitsi in my RN app. I made a native bridge to the RN and tried to make a video call using jitsi. I have implemented iOS SDK as well and made a bridge to RN and it's running properly. but don't know what is problem with the android? I have followed all the steps from the documentation. Thank you.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing. Since the original issue we have released an actual RN SDK which fixes many of the shortcomings of using our native SDK in an Android app.