Rocket.Chat.ReactNative: [Bug][Jitsi] Users can't login Jitsi call with 40+ participants since 4.12.1 version on Andriod

Description:

Users can not join any big Jitsi call since 4.12.1 Using Jitsi meet applications they can join

Environment Information:

  • Rocket.Chat Server Version: 3,7,1
  • Rocket.Chat App Version: 4.13.0.21833
  • Device Name: Xiaomi Mi 9 SE
  • OS Version: Android 10

Steps to reproduce:

  1. Create 20+ participants Jitsi call in Google Chrome using Invite more people feature and copy and paste call URL multiple times to new tabs
  2. Click Click to Join button in RC RN applications
  3. Application become unresponsive, all buttons and menu are unresponsive, you can hear sounds like someone joins call, but you can’t, you stuck

Expected behavior:

Users need to connect to any Jitsi call using RC RN application.

Actual behavior:

20201208_120623

Old RCRN 4.7 version (whitelabel) still joins that big calls without any troubles. And I did try Jitsi Meet application to join call by link - success! 2020-12-08T05_12_14

But Rocket Chat React Native application can not join to that big call for some reason.

Additional context:

I think, it may be related to default Tile View since some Jitsi server version and some Jitsi SDK version. Old 4.7 still using Stage View and connects without any issues.

And if I somehow can join call using RCRN application - it doesn’t work well. I enabled camera and see myself on smartphone, others see my user with connection issues: image image Buttons in that case are working for others - if I turn mic off - all other users see mic crossed icon, and camera same: image And one more strange thing here. I connected to that call using Jitsi meet mobile application and both mobile clients (RCRN 4.12.1 and Jitsi Meet) see each other video and hear voices. Bot mobile clients in same WiFi network. when all calls web clients in a different network. And web clients see only video by Jitsi Meet clent.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 19 (17 by maintainers)

Most upvoted comments

Hey, @ankar84. We weren’t able to reproduce it. We’ve tried with 30+ participants and everything worked fine. Different than the usual video conferencing, Jitsi decodes videos on the clients rather than the server, so it takes a higher amount of memory and CPU. Next time you see this error, capture a bug report and send us. With that in hands, we’ll be able to inspect if it’s a memory overflow or something else. Thanks!

I must reopen that issue - proof of bug is sent to Diego at open server. Newest version 4.15.0.23346 involved

Same reports on this issue from multiple users in our school, without changing anything except the app version.

Can you please give more details (Jitisi server info, mobile clients info) and screenshots? Developers could not reproduce that issue on their Jitsi server

Yeah… that’s the nasty kind of bugs.

Jitsi-Server:

dpkg -l | grep jitsi
ii  jitsi-meet                    2.0.5076-1                   all          WebRTC JavaScript video conferences
ii  jitsi-meet-prosody            1.0.4428-1                   all          Prosody configuration for Jitsi Meet
ii  jitsi-meet-turnserver         1.0.4428-1                   all          Configures coturn to be used with Jitsi Meet
ii  jitsi-meet-web                1.0.4428-1                   all          WebRTC JavaScript video conferences
ii  jitsi-meet-web-config         1.0.4428-1                   all          Configuration for web serving of Jitsi Meet
ii  jitsi-videobridge2            2.1-351-g0bfaac1c-1          all          WebRTC compatible Selective Forwarding Unit (SFU)

uname -a
Linux xxx 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux

is not the latest 2.0.5142 version because of this bug: https://github.com/RocketChat/Rocket.Chat.Electron/issues/1919

RocketChat App Version: 4.12.1 (mostly… I also have some users with a fairly lower update priority…) It only happened for iOS/Android App users not on Linux/Mac/Windows - and also not with the Jitsi app.

I already tested this for a couple of days without token-auth, and it didn’t matter whether the server was running 10 conferences with a total of ~340 participants or 2 with only ~50 participants.

The RocketChat App show the same behaviour as in your GIF, never ending loading screen…