Create HttpSignalingSettings with providing iceServers.
Call ParseArguments on the HttpSignalingSettings without any IceServerUrl parameters defined.
The first iceServer will have it's urls replaced with nulls.
For an application, this could be replicated by running the application with command line arguments that weren't related. In my case, running an application with -force-vulkan would cause it to replace the iceServerUrls.
Description of the changes:
The commandline parser was returning an empty list when parsing the URL parameters when none were provided on the command line. As a result, the HttpSignalingSettings class would replace the URLs with empty ones since it thought the values were set. This would then later cause issues when connecting since the ice candidate URL is null.
How this was tested:
Tested by updating, and running Unit tests.
Tested by running an application that was providing iceServerUrls, and command line arguments that were unrelated.
How to reproduce:
Description of the changes:
How this was tested: