Failed to add ICE candidate

[shashipatil]

Getting following issues in the build when tried

1. Failed to add ICE candidate
2. Failed to set remote answer sdp: called in wrong state: kStable

[DipanshKhandelwal]

Can you please add steps to help me reproduce it ?

I remember seeing this issue before, but it was solved by this.

[shashipatil]

For me it's happening. Steps to reproduce device 1 1)Create room 2) enter into join screen device 2 1) Create the same room as created for device 1 2) enter into call screen 3) initiate call 4) receive the call in device 1

…

On Tue, 8 Sep 2020 at 11:47, Dipansh Khandelwal ***@***.***> wrote: Can you please add steps to help me reproduce it ? I remember seeing this issue before, but it was solved by this <6934ad3> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAZDYJ77W7LRDX4FTCA27DSEXD6HANCNFSM4Q7PITOA> .

[DipanshKhandelwal]

Can you try changing the sequence of the steps ?

Device 1

• Enter the call screen first.
• Start Call

Device 2

• Enter join screen
• Join Call

Try to start call first and then join it.

[shashipatil]

Getting same issue and even i am getting Reference error as Can't find variable: calleeCandidatesCollection

…

On Tue, 8 Sep 2020 at 16:27, Dipansh Khandelwal ***@***.***> wrote: Can you try changing the sequence of the steps ? *Device 1* - Enter the call screen first. - Start Call *Device 2* - Enter join screen - Join Call Try to start call first and then join it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAZDYKCUQ4FXUGRYUAK3HLSEYE2DANCNFSM4Q7PITOA> .

[shashipatil]

call is initiated but error are coming

…

On Tue, 8 Sep 2020 at 16:37, shashi patil ***@***.***> wrote: Getting same issue and even i am getting Reference error as Can't find variable: calleeCandidatesCollection On Tue, 8 Sep 2020 at 16:27, Dipansh Khandelwal ***@***.***> wrote: > Can you try changing the sequence of the steps ? > > *Device 1* > > - Enter the call screen first. > - Start Call > > *Device 2* > > - Enter join screen > - Join Call > > Try to start call first and then join it. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#4 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADAZDYKCUQ4FXUGRYUAK3HLSEYE2DANCNFSM4Q7PITOA> > . >

[DipanshKhandelwal]

I am sorry, I tested it again to be sure, and it works fine without any of the mentioned issues.
You can possibly test:

• You have updated code.
• Firebase connection is fine.
• Firebase Firestore rules allow you to write on the database.

Please share some code snippets or error logs, which can help recognise the issue.
And if you can help me reproduce it, that would be better.
Thanks.

[umairlive490]

I also get this error.
1.Failed to add ICE candidate
2.Failed to set remote answer sdp: called in wrong state: kStable
but sometimes call is connected successfully