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
WebRTCModule.peerConnectionInit returns false when using TURN server with iceServers key "urls" #1476
Comments
Additional info: export default class RTCPeerConnection extends EventTarget<RTCPeerConnectionEventMap> {
...
constructor(configuration) {
super();
this._pcId = nextPeerConnectionId++;
console.log("this._pcId", this._pcId);
let peerCon = WebRTCModule.peerConnectionInit(configuration, this._pcId);
console.log("peerCon", peerCon);
if (!peerCon) {
throw new Error('Failed to initialize PeerConnection, check the native logs!');
}
...
}
...
} |
Thanks for the report! |
What error do you see in logcat? This is the code for parsing ICE servers (WebRTCModule.java):
We don't check for |
There was nothing useful in Logcat. You're right, it was an issue with the case. |
Im reopening so we can fix this. |
- Make sure the `urls` property is used, while supporting the deprecated `url`. - Make sure all servers are lower-case since the C++ layer does a case insensitive parse. Fixes: #1476
Fix here: #1477 I chose to sanitize them on the JS side since that way we don't need to fix it twice on the native side. |
- Make sure the `urls` property is used, while supporting the deprecated `url`. - Make sure all servers are lower-case since the C++ layer does a case insensitive parse. Fixes: #1476
I spent many days trying to debug this issue, now I feel silly it's this simple, but I don't believe this is the expected behavior.
Expected Behavior:
peerConnection
initializesObserved Behavior:
App crashes with error message
Failed to initialize PeerConnection, check the native logs!
.Steps to reproduce the issue:
According to w3 docs (MDN) the
RTCIceServer
Dictionary's key should be "urls". Using "url" should still be supported, in my opinion.Platform Information
0.72.6
^111.0.6
~49.0.18
The text was updated successfully, but these errors were encountered: