WebRTC library version

Last Update: 2016-09-10 +0

This thread is for discussion about upgrade/maintain webrtc version

The webrtc library of this repository is based on webrtc-build-script opensourced and maintained by pristine and it seems pristine is no longer maintain the auto-build but webrtc-build-script

WebRTC Library git revision build Info

webRTC git branch mapping revision:

wertc git repo chrome release history wiki

45 -> #9565 46 -> #9745 47 -> #10155 48 -> #10622 49 -> #11252 50 -> #11765 51 -> #12279 52 -> #12798 53 -> #13317 ( Stable ) 54 -> #13869 ( Beta )

Latest pre-build binary from pristine

The version of webrtc we use in this repository currently is likely between chrome 47-rc and 47-stable.

ANDROID:

webRTC svn version: 11139
GIT COMMIT: 0c7e9f540b282d60b94081f601a1694054d8646e
maven: http://mvnrepository.com/artifact/io.pristine/libjingle
download: https://repo1.maven.org/maven2/io/pristine/libjingle/

IOS:

webRTC svn version: 11177
GIT COMMIT: 893505d0fb41a840be5e4a44a1250dba83d79bf5
cocoapods: https://cocoapods.org/pods/libjingle_peerconnection/
cocoapos: https://github.com/CocoaPods/Specs/blob/master/Specs/libjingle_peerconnection/
download: https://s3.amazonaws.com/libjingle/11177/Release/0/libWebRTC.tar.bz2

[zxcpoiu]

I totally agree with you that using pod is easier to install than manually link it on library such as this. The only problem I guess in this moment is, we can not find a maintained neither on cocoapods nor maven.

as noted in first comment, the maintainer of libjingle-peerconnection on both cocoapods and maven are the same team of webrtc-build-script, and both stop updated roughly at version 11139~11177 since Jan, 2016.

to get things work, it would be:

1. find the hosting repo ( both cocoapods and maven ) :
   • ask them for update.
   • create another one maintained by ourselves. ( is it necessary? )
2. compile native library into pod/aar format
3. provide documents for how to apply it.

obviously, we all have our own full time shits to do, would you mind take care cocoapods part and I would dealing with android aar?

or someone has interest in it?

I would happy to see it happens 😄

[inspiraluna]

Sorry again to make it more clear. Some networks don’t support stun, if thats the case works everything should or must work over turn. so you need a TURN server. please test both environments. TURN in my case is a bit slower in performance wich is natural. but still seems as fluent as in android. (at least it seems like that in most of the cases) I do not have any worries as long as reflexive connectivity works. Please check environments with turn only possibilities on ALL peers (not just on one)!

Let me know!

N.

Am 20.10.2016 um 08:46 schrieb Santi Iglesias [e-mail]:

@inspiraluna https://github.com/inspiraluna I have exactly the same issue you talked about… And I am stuck here trying to switch that library with updates with no luck, How did you solve it? I need to get it working

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oney/react-native-webrtc/issues/79#issuecomment-255022897, or mute the thread https://github.com/notifications/unsubscribe-auth/AART4sZtlsijEOjPPeOFT5P1Se7bgNTxks5q1w5WgaJpZM4ImMCz.