-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Failed to set local offer sdp: Called in wrong state: STATE_RECEIVEDINITIATE #286
Comments
This might be a duplicate of #269. Does the error actually cause peerjs to stop working? |
Hi @semigroupoid, yes it does. I cannot have an established video call connection. |
Hi I also got the same exception . Can anyone help me in fixing it . |
Just had this happen now. |
Hi, |
When it happens the way I fix it is restarting the computer that didn't crash, my understanding is it's probably storing some ice candidates and trying to connect the fastest way possible while the other side isn't prepared yet. Didn't try a simple browser restart though (simple page refresh doesn't work) |
I'm getting this as well, but on Chrome to Chrome connections. Doesn't seem to prevent the clients from connecting OK however. |
Getting the same problem Chrome to Chrome. Any solutions yet? |
## Failed to set local offer sdp: Called in wrong state: STATE_RECEIVEDOFFER in android Native Develpment |
Restarting the (chrome) browser made the problem go away for me, and I was able to make calls again |
## Failed to set local offer sdp: Called in wrong state: kHaveRemoteOffer in android native WebChromeClient. Any solution? |
+1, have |
Am also getting the same error peer.min.js:1 PeerJS: ERROR Error: (OperationError) Failed to set local offer sdp: Called in wrong state: kHaveRemoteOffer Any solution for this? |
https://gitlab.com/zkry.akgul/peerjs
Use this instead of orginal lib. I made little touchs to lib files and
seems like problem solved.
------------------------
Zekeriya AKGÜL
Sreekanthp74 <notifications@github.com>, 16 Tem 2018 Pzt, 09:49 tarihinde
şunu yazdı:
… Am also getting the same error
peer.min.js:1 PeerJS: ERROR Error: (OperationError) Failed to set local
offer sdp: Called in wrong state: kHaveRemoteOffer
peer.min.js:1 PeerJS: Failed to setLocalDescription, (OperationError)
Failed to set local offer sdp: Called in wrong state: kHaveRemoteOffer
Any solution for this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#286 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APa-mKrHOdYzFnPTgsufeySFuT_v5MSdks5uHDd-gaJpZM4EQ5df>
.
|
Could you test with the latest build from master branch? in "dist" folder. https://raw.githubusercontent.com/peers/peerjs/master/dist/peer.min.js |
Nope i couldn't. I work on it couple months ago and use it my small range
project. It was worked for me.
16 Tem 2018 Pzt 10:49 tarihinde Jairo Caro-Accino Viciana <
notifications@github.com> şunu yazdı:
… Could you test with the latest build from master branch? in "dist" folder
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#286 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APa-mCcM4rP4UlXRkoWKR53JZbiTY4ZRks5uHEV9gaJpZM4EQ5df>
.
|
Thanks but , @kidandcat Took it from the master git repo of peer js , it is working fine |
Mmm, it should be the same file, maybe your browser is catching it with an older version. Anyway, feel free to reopen if you get the error again. Also I published the changes to NPM so you can use latest version from NPM now. |
Now I have this issue: "OperationError: Failed to set local offer sdp: Called in wrong state: kHaveRemoteOffer". Trying to make connection between two browsers on one computer. @kidandcat can you help me with this? |
Which PeerJS are you using? |
@kidandcat 0.3.14 |
Update it, latest is 0.3.16 |
@kidandcat the error has gone! but still no audio. and this is how I revieve it: |
This issue occurs at times when Firefox v38 makes an attempt to call Chrome v42 and with Temasys AdapterJS integration when IE v11 is the one starting the call with Chrome v42.
The text was updated successfully, but these errors were encountered: