Conversation
# Conflicts: # ios/Podfile.lock # yarn.lock
105c3d6 to
5984ccb
Compare
d752315 to
be22c94
Compare
android/build.gradle
Outdated
| libre_build = !(isPlay.toBoolean()) | ||
| jitsi_url = isPlay ? "https://github.com/RocketChat/jitsi-maven-repository/raw/master/releases" : "https://github.com/RocketChat/jitsi-maven-repository/raw/libre/releases" | ||
| jitsi_version = isPlay ? "2.10.2" : "2.10.0-libre" | ||
| jitsi_url = isPlay ? "http://github.com/RocketChat/jitsi-maven-repository/raw/3.7.0/releases" : "https://github.com/jitsi/jitsi-maven-repository/raw/libre/releases" |
There was a problem hiding this comment.
We're not actively maintaining libre, so I just changed the URL to match, but there's no point to test at this time.
| const { route } = this.props; | ||
| const { userInfo } = this.state; | ||
|
|
||
| if (isIOS) { |
There was a problem hiding this comment.
I'm calling Jitsi on iOS the old way and Android using props.
For some reason I didn't understand, Android is not working this way anymore.
app/views/JitsiMeetView.js
Outdated
| onConferenceJoined={this.onConferenceJoined} | ||
| style={sharedStyles.container} | ||
| style={StyleSheet.absoluteFill} | ||
| options={options} |
There was a problem hiding this comment.
This is what triggers the call on Android from now on.
ios/Podfile
Outdated
| abstract_target 'defaults' do | ||
| # force use our own JitsiMeetSDK | ||
| pod 'JitsiMeetSDK', :git => 'https://github.com/RocketChat/jitsi-meet-ios-sdk-releases.git' | ||
| pod 'JitsiMeetSDK', :git => 'https://github.com/RocketChat/jitsi-meet-ios-sdk-releases.git', :branch => '3.7' |
There was a problem hiding this comment.
We need to remove this branch and reinstall pods before merging
Yeap, it's a front-end bug, that will be fixed in next release, I guess |
And that's really strange. I didn't get that kind of bug using Jitsi meet application which on same 3.7.0 SDK version. But I will wait RCRN Experimental beta to test it with our production Jitsi deployment and left a feedback for sure! |
3098cd5 to
ec8182f
Compare
|
Downgraded to Jitsi SDK 3.6.0 and there's no ghost users or black screen. |
Good to know that! Wait to test public beta with Jitsi SDK 3.6.0! |
# Conflicts: # ios/Pods/Pods.xcodeproj/project.pbxproj # ios/Pods/Target Support Files/Pods-NotificationService/Pods-NotificationService.debug.xcconfig # ios/Pods/Target Support Files/Pods-NotificationService/Pods-NotificationService.release.xcconfig
# Conflicts: # ios/Pods/Pods.xcodeproj/project.pbxproj
Proposed changes
Updates Jitsi SDK to 3.6.0.
All forks were updated.
Issue(s)
Depends on:
RocketChat/react-native-jitsi-meet#9
RocketChat/jitsi-maven-repository#2
RocketChat/jitsi-meet-ios-sdk-releases#5
RocketChat/jitsi-meet#14
How to test or reproduce
Starting a call
Joining from message
Joining from push notification
Test Jitsi features
Dark mode
Screenshots
Types of changes
Checklist
Further comments