Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Creating new peer; INVALID:ICE pwd has space
See original GitHub issueWhen creating a new peer, sometimes, the ICE password is created with a space, which throws an error as space character is not allowed.
Error: InvalidAccessError: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Failed to apply the description for 0: Invalid ICE parameters: ICE pwd must contain only alphanumeric characters, '+', and '/'.
I am stringifying the data to send through Pusher.io (as it doesn’t accept objects as the data). Could this be an issue with stringifying and then parsing, or is this an issue with simple-peer generating incorrectly formatted ICE password?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I opted to check the SDP before its sent through Pusher. Turns out that the sdp being created generates the pwd: 1lkMoNSenQycEXa+aH7fAu0u
Whereas the sdp that get received after going through pusher.io comes back as: 1lkMoNSenQycEXa aH7fAu0u
The + is missing…
I am assuming that this is something to do with Pusher, and how they parse data. Anyways thanks for the info and help.
Go to
chrome://webrtc-internalsif it is Chrome orabout:webrtcif it is Firefox and see what was actually generated by the browser and compare to what you see in signaling.