Unity 2019.3.x Does not parse CommandLineArgs as expected
I have a project that gets launched via a desktop application. In doing so it receives a set of arguments to let the app know if it is a guest or a signed in user among others.
Since updating the project to 2019.3 it does not seem to parse the arguments correctly. Specifically the command to launch:
"D:\Builds\LiveBuilds\test folder\LIVE.exe"
Which gets split up into two because of the gap between the folder name. So the first two arguments instead of being {D:\Builds\LiveBuilds\test folder\LIVE.exe} {true}
instead become: {D:\Builds\LiveBuilds\test} {folder\LIVE.exe}
I have asked this question on stack overflow that gives it a bit more in depth to what is being passed over but to save you a click the data being passed in is:
"D:\Builds\LiveBuilds\test folder\LIVE.exe" true test test
This equates to the path of the app to launch it, whether the user is a guest, and then in this case the first name and company name.
Is there a reason why this core system functionality suddenly does not work in Unity 2019.3? IS there something I am missing in settings? Thanks.
Your answer
Follow this Question
Related Questions
Unity Error Please I need Help 0 Answers
Can I run this(pretty please?) 0 Answers
NotImplementedException: Unmanaged activation is not supported 0 Answers
How to patch on Windows build game 0 Answers