New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 7 users
Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
NextAction: ----
OS: ----
Pri: 3
Type: Bug
sdp



Sign in to add a comment
"Error: An invalid or illegal string was specified" should provide more information
Reported by cow...@bbs.darktech.org, Oct 29 2013 Back to list
Chrome 30.0.1599.101

1. Invoke addIceCandidate() with:

{
  "sdpMLineIndex": 0,
  "sdpMid": "audio",
  "candidate": "a=candidate:3013953624 1 udp 2113937151 192.168.1.100 61193 typ host generation 0\r\n"
}

2. An error is thrown: "Error: An invalid or illegal string was specified"

I am expecting the error to explain what exactly is wrong with the value of the candidate (ideally including line/column numbers).
 
I forgot to mention: the error message should include the invalid string (as context) so we don't have to chase the error back to its source.
http://stackoverflow.com/a/17424224 pointed me in the right direction. It hinted that I am invoking addIceCandidate() before setRemoteDescription() and indeed this is the case. So to resolve this issue I expect error message to say something along the lines of "addIceCandidate() invoked before setRemoteDescription()" instead of "Error: An invalid or illegal string was specified" as it does now.

The current message is misleading because the string itself is perfectly legal.
Project Member Comment 3 by braveyao@webrtc.org, Oct 30 2013
Mergedinto: 2556
Status: Duplicate
I suppose it's better to add all your error message requests into one issue. Merge this into  issue 2556 .
Sounds good. I'll add notes to the main issue to ensure that the evaluator doesn't forget to visit the sub-issues.
Comment 5 by wu@webrtc.org, Jan 17 2014
Labels: Mstone-34
Mergedinto:
Owner: wu@webrtc.org
Status: Assigned
Re-open as 2556 only covers the set*description case.
Comment 6 by wu@webrtc.org, Jan 17 2014
Labels: Area-PeerConnection
Comment 7 by wu@webrtc.org, May 21 2014
Labels: -Mstone-34 Mstone-38
Comment 8 by wu@webrtc.org, Jul 25 2014
Labels: sdp
Comment 9 by wu@webrtc.org, Jul 28 2014
Owner: pthatcher@webrtc.org
Assign to Peter for triage.
Comment 10 by vrk@webrtc.org, Oct 16 2014
Labels: -Mstone-38 IceBox EngTriaged
Project Member Comment 11 by tnakamura@webrtc.org, Nov 4 2015
This bug hasn't been modified for more than a year. Is this still a valid open issue?
The testcase provided in the initial description is extremely simple so you should be able to test on your end.

For my part, I've been off WebRTC projects for over a year so I no longer have a test environment to work with.
Project Member Comment 13 by pthatcher@webrtc.org, Nov 8 2016
Labels: Pri-3
Sign in to add a comment