-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
The Problem of Jitsi Meet app in Google Play #2658
Comments
Unfortunately that's a bit hard to tell. Due to limitations on access to signing keys we build the apps on a secure Atlassian machine, which uses a clone of this project with added signing keys and the Crashlitics framework. That said, building the current master should always work, if it doesn't that's a bug which we should address. Are you encountering any problems? |
@saghul |
@saghul
E/AndroidRuntime: FATAL EXCEPTION: main |
Hum, are you just building our app or using the SDK? Are you using meet.jit.si or your own deployment? |
The app from the store and this repo are in essence the same, so I'm a bit puzzled as to what's going on here :-( |
@saghul I find the app from the store is different with this repo, The app from the store can't setting display name and server url... |
Ah, that'd the old version then (I thought we had pushed the new one, I've been away for 6 weeks, sorry). Then this is a regression from the WebRTC M58 to M63 upgrade. |
@saghul I need to change back to M58? How to do? I find about WebRTC in package.json is "react-native-webrtc": "github:jitsi/react-native-webrtc#626818af40384356617f70366133317b6a475171", |
Here is a discussion about ‘ rotation’ facebook/react-native#3216 @saghul |
I don't think that's the bug here, since we don't use that, AFAIK.
You need to "go back in time". That is, reset your clone to a commit which didn't have M63 as a dependency. This should do:
And then Note that this is not future-proof, you should try to fix the bug itself. Unfortunately I have no device where I can reproduce this, but I'll happily review a PR. |
Yep, I mean to reset your clone of jitsi-meet itself. |
@saghul I do as you said using 41aa704 |
I really don't know :-( All I can suggest is "going back in time" until you find a revision that works and trying to find the culprit. It might have been an update to react-native-webrtc, not related to the M63 upgrade, but it's hard to tell. |
@saghul I find the version of react-native update from 0.50.4 to 0.51.0,Maybe react-native-webrtc upgrade |
I doubt this is related to the react-native version but feel free to try! |
@saghul I want to try react-native version 0.50.4 and 0.51.0 with the master version of jitsi-meet by change the package.json and package-lock.json. Could you tell am I right only change package.json and package-lock.json, and do: |
Ok, now that we narrowed it down, the problem seems to be the fact that there is only a single camera. Closing this in favor of #2209 . |
Could you tell me which version of source code do you use for compilation of the Jitsi Meet app in Google Play? Thanks!
The text was updated successfully, but these errors were encountered: