jitsi-meet: Jitsi master branch not functional on Android due "Invariant Violation" errors
Description:
Current master branch is not functional on Android due TypeError and “Invariant Violation”
Steps to reproduce:
- git clone
- npm install
- start Android Studio 2022.2.1
- open project directory “android”
- build “Make project”
- run Metro with “npx react-native start”
- run App in Android studio in emulator
Expected behavior:
Android studio will build app and run in emulator
Actual behavior:
` WARN ‘new NativeEventEmitter()’ was called with a non-null argument without the required ‘addListener’ method. WARN ‘new NativeEventEmitter()’ was called with a non-null argument without the required ‘removeListeners’ method.
INFO 2023-05-19T16:13:27.637Z [modules/browser/BrowserCapabilities.js] This appears to be react-native, ver: 0.69.10
ERROR TypeError: undefined is not an object (evaluating ‘error.stack.split’)
LOG Running “App” with {“initialProps”:{“flags”:{“pip.enabled”:true,“call-integration.enabled”:false,“server-url-change.enabled”:true,“resolution”:360,“welcomepage.enabled”:true},“timestamp”:1684512776946,“url”:{“serverURL”:“https://meet.jit.si”,“config”:{}}},“rootTag”:1}
ERROR Invariant Violation: “App” has not been registered. This can happen if: Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project. A module failed to load due to an error and ‘AppRegistry.registerComponent’ wasn’t called.
ERROR Invariant Violation: “LogBox” has not been registered. This can happen if: Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project. A module failed to load due to an error and ‘AppRegistry.registerComponent’ wasn’t called. `
Server information:
- Jitsi Meet version: master
- Operating System:
Client information:
- Browser / app version: master
- Operating System: Gentoo Linux
Additional information:
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 32 (15 by maintainers)
That is NOT a mobile release.
Please use the mobile app or SDK tags.
I’ll be honest, simulators are not great to test most of the things RTC related, no this problem is not high priority, sorry.
Yes, we have plans to update shortly!