Video stream interlocutor remains in black screen

[j20mc]

Which platform(s) does your issue occur on?

• Android

Please, provide the following version numbers that your issue occurs with:

• Demo

Please, tell us how to recreate the issue in as much detail as possible.

• Demo

Is there any code involved?

• Demo and V2

Hi there, I currently have a video stream problem that remains black during a call. The sockets communicate well but there is no video stream. I had problems with my application and I just tested on your demo and I have the same problem.

Here is the console log of your demo =>

APPLICATION :

{
JS:   "_observers": {},
JS:   "dataChannels": {},
JS:   "remoteIceCandidates": [],
JS:   "inCall": false,
JS:   "isInitiator": false,
JS:   "connection": {
JS:     "_remoteDescription": null,
JS:     "_localDescription": null,
JS:     "android": {}
JS:   },
JS:   "me": "45f5f8f5-33ce-bd12-8bae-9f338a6769c8",
JS:   "socket": {
JS:     "socket": {}
JS:   }

JS: call:incoming to: 20d5c949-67a8-83d8-87e6-6a8519254d0a from: 45f5f8f5-33ce-bd12-8bae-9f338a6769c8
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:answered
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate
JS: call:iceCandidate

SERVER :

Connected: -> OIMOHepKBiNd35BHAAAF
User Connected: -> hKwbvt7KiKS-_ORUAAAG
call from e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:iceCandidate e96223c3-63d5-2375-a355-104c891a4e53
call:answered e433a775-203c-873e-b75f-64188ab94e2f
call:iceCandidate e433a775-203c-873e-b75f-64188ab94e2f
call:iceCandidate e433a775-203c-873e-b75f-64188ab94e2f
call:iceCandidate e433a775-203c-873e-b75f-64188ab94e2f
call:iceCandidate e433a775-203c-873e-b75f-64188ab94e2f
call:iceCandidate e433a775-203c-873e-b75f-64188ab94e2f
call from e433a775-203c-873e-b75f-64188ab94e2f

As you can see, there is no error but the video stream between the two smartphones remains in black. I specify that each smartphone has its own video stream but it does not have that of the interlocutor.

[triniwiz]

What type of connection are you using mobile or WiFi

[j20mc]

I use a 4G mobile connection for my mobile and my pc wifi

[triniwiz]

There are a couple things you can try

1. Try both on WiFi
2. Try calling the web demo
3. Try another stun server even turn if you have access to one

[j20mc]

Ok, I will try your advice and come back to you

[j20mc]

I did several tests with always the same problem.

• Same Wifi for both smartphones and the pc.
• Same 4G mobile connection for both smartphones and pc.
• I put the server application on one of my servers.
• I put the server application online via ngrok.
• I did not use the web demo (I don't know how to launch it).

[triniwiz]

Since you only mentioned the video stream the audio works fine ?

[j20mc]

Sorry, video & audio doesn't work

[triniwiz]

Ok good to know also ensure you’re using the standard example not the basic (which should be the deprecated v1) another thing to verify is https://github.com/triniwiz/nativescript-webrtc/blob/master/demo/app/standard/standard-vm.ts this is firing to add the incoming candidates

[j20mc]

I am using your file well and I have the iceCandidate displayed on the console. I also use the standard and not the basic.
I have been trying to find out why there is this problem for several days, but I decided to ask for help

[triniwiz]

Yes I’m seeing it logged but can you add some extra logging to verify the add method is being called ?

[j20mc]

addIceCandidate is called

[j20mc]

call:incoming to: 3e861fde-0f22-9241-9479-95f9f6ddf26e from: 7eb009d4-c608-1ff5-a1c3-4f6c96121eb2
JS: call:iceCandidate
JS: candidate candidate:4099077385 1 udp 2122260223 192.168.3.87 48023 typ host generation 0 ufrag jWQ5 network-id 3 network-cost 10
JS: call:iceCandidate
JS: candidate candidate:559267639 1 udp 2122202367 ::1 54376 typ host generation 0 ufrag jWQ5 network-id 2
JS: call:iceCandidate
JS: candidate candidate:1510613869 1 udp 2122129151 127.0.0.1 58425 typ host generation 0 ufrag jWQ5 network-id 1
JS: call:iceCandidate
JS: candidate candidate:4099077385 1 udp 2122260223 192.168.3.87 55760 typ host generation 0 ufrag jWQ5 network-id 3 network-cost 10
JS: call:iceCandidate
JS: candidate candidate:559267639 1 udp 2122202367 ::1 37523 typ host generation 0 ufrag jWQ5 network-id 2
JS: call:iceCandidate
JS: candidate candidate:1510613869 1 udp 2122129151 127.0.0.1 56640 typ host generation 0 ufrag jWQ5 network-id 1
JS: call:iceCandidate
JS: candidate candidate:1876313031 1 tcp 1518222591 ::1 44656 typ host tcptype passive generation 0 ufrag jWQ5 network-id 2
JS: call:iceCandidate
JS: candidate candidate:344579997 1 tcp 1518149375 127.0.0.1 47123 typ host tcptype passive generation 0 ufrag jWQ5 network-id 1
JS: call:iceCandidate
JS: candidate candidate:1876313031 1 tcp 1518222591 ::1 50444 typ host tcptype passive generation 0 ufrag jWQ5 network-id 2
JS: call:iceCandidate
JS: candidate candidate:344579997 1 tcp 1518149375 127.0.0.1 58483 typ host tcptype passive generation 0 ufrag jWQ5 network-id 1
JS: call:answered
JS: call:iceCandidate
JS: candidate candidate:2787615239 1 udp 2122260223 10.250.96.80 44201 typ host generation 0 ufrag oXIG network-id 3 network-cost 900
JS: call:iceCandidate
JS: candidate candidate:559267639 1 udp 2122202367 ::1 37909 typ host generation 0 ufrag oXIG network-id 2
JS: call:iceCandidate
JS: candidate candidate:1510613869 1 udp 2122129151 127.0.0.1 45265 typ host generation 0 ufrag oXIG network-id 1
JS: call:iceCandidate
JS: candidate candidate:1876313031 1 tcp 1518222591 ::1 41755 typ host tcptype passive generation 0 ufrag oXIG network-id 2
JS: call:iceCandidate
JS: candidate candidate:344579997 1 tcp 1518149375 127.0.0.1 40995 typ host tcptype passive generation 0 ufrag oXIG network-id 1

[triniwiz]

Can you bind to the onConnectionStateChange event also use connectionState (really iceConnectionState will be renamed in the future) on the peerconnection it should tell you a bit more what's happening https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/iceConnectionState

[j20mc]

Ok, I will try your advice and come back to you

[j20mc]

I cannot link the onConnectionStateChange event to use connectionState. I think I lack a practice on the subject. But The function onConnectionStateChange is called only once per smartphone per call

This function blocks communication without making an error =>

this.connection.onConnectionStateChange(() => { console.log("EVENT LISTENER STATE CHANGE", this.connection.connectionState)})