This message was deleted.
# helpdesks
steep-balloon-41261
01/13/2023, 12:58 PMThis message was deleted.
m
magnificent-art-43333
01/13/2023, 4:26 PMHey there, these are asynchronous calls. You probably need to async/await them or chain them in promise callbacks. For network requests, you can’t be 100% sure of the order these operations arrive and execute on the server.
b
bright-tiger-35509
01/13/2023, 4:28 PMIn desktop livekit client it works as expected
bright-tiger-35509
01/13/2023, 4:28 PMI mean the js client
m
magnificent-art-43333
01/13/2023, 4:28 PMAre you running locally?
b
bright-tiger-35509
01/13/2023, 4:28 PMYes
m
magnificent-art-43333
01/13/2023, 4:29 PMTry awaiting and see what happens?
b
bright-tiger-35509
01/13/2023, 4:29 PMOkay
bright-tiger-35509
01/13/2023, 4:30 PMWill try
m
magnificent-art-43333
01/13/2023, 4:30 PMI’m not familiar with RN, so maybe there’s something about it I don’t understand. cc @eager-raincoat-52616 just in case.
e
eager-raincoat-52616
01/13/2023, 4:38 PMHmm dont know of any differences here that would cause a behavior change here on RN.
d
dry-elephant-14928
01/13/2023, 7:45 PMwhat is
desktop livekit clientb
bright-tiger-35509
01/17/2023, 9:08 AMI mean the js client
d
dry-elephant-14928
01/17/2023, 5:18 PMthat's interesting.. could you file an issue on GH for this? we'll take a deeper look as to what the issue may be.
b
bright-tiger-35509
01/19/2023, 1:07 PMokay
bright-tiger-35509
01/19/2023, 1:09 PMi guess the problem is with react-native-webrtc or the way I am using it, it doesnt stop the previous negotiation when I start another in between the first negotiation, or doesnt synchronize the 2 negotiations.
bright-tiger-35509
01/19/2023, 1:09 PMcc @dry-elephant-14928
d
dry-elephant-14928
01/20/2023, 12:56 AMOur SDK should manage that. If it's in the middle of a negotiation, it would wait for it to be complete before starting another one.
5 Views