--workDir argument is not being escaped when passed to JRE
Launcher is displaying blank screen when receiving a --workDir argument with a space in the path. The argument is being passed into the native launcher with quotes: (e.g. --workDir "C:\users\Greg Lary\Minecraft\"). See attached nativelog.txt
What I expected to happen was...:
That the native launcher would relay to the --workDir argument to the JRE with quotes around the path.
What actually happened was...:
When the native launcher invokes the JRE to execute the launcher application, no quotes are applied to the parameter leading to a malformed launch environment.
Steps to Reproduce:
1. Install native launcher in a folder with a space in it
2. Execute minecraft.exe in the form of:
minecraft.exe --workDir "C:\users\long name\Documents\Minecraft". See attached nativelog.txt
Environment
Windows 7, Windows 8, Windows 8.1
Created Issue:
--workDir argument is not being escaped when passed to JRE
Launcher is displaying blank screen when receiving a --workDir argument with a space in the path. The argument is being passed into the native launcher with quotes: (e.g. --workDir "C:\users\Greg Lary\Minecraft\"). See attached nativelog.txt
What I expected to happen was...:
That the native launcher would relay to the --workDir argument to the JRE with quotes around the path.What actually happened was...:
When the native launcher invokes the JRE to execute the launcher application, no quotes are applied to the parameter leading to a malformed launch environment.Steps to Reproduce:
1. Install native launcher in a folder with a space in it
2. Execute minecraft.exe in the form of:
minecraft.exe --workDir "C:\users\long name\Documents\Minecraft". See attached nativelog.txtEnvironment
Windows 7, Windows 8, Windows 8.1
Is this still a concern in the current Minecraft Launcher version 2.0.805 / 2.0.806? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. It will be reopened it as soon as the requested information has been delivered.