Search Issue Tracker

By Design

Votes

1

Found in

2021.3.38f1

2022.3.27f1

6000.0.1f1

Issue ID

UUM-71165

Regression

Yes

Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path

-

Reproduction steps:
1. Open the Windows command prompt
2. Run a command to open a Unity project, including a backslash at the end of the project path
Example: > [Unity_Path]\[version]\Unity.exe -projectPath "G:\project\"
3. Observe the screen

Expected result: The desired Unity project opens
Actual result: The Unity Hub opens

Reproducible with: 2021.3.29f1, 2021.3.38f1, 2022.3.9f1, 2022.3.27f1, 6000.0.1f1
Not reproducible with: 2021.3.28f1, 2022.3.8f1

Reproducible on: Windows 11
Not reproducible on: No other environment tested

Workaround: Run the command without the backslash to open the project
Example: > [Unity_Path]\[version]\Unity.exe -projectPath "G:\project"

  1. Resolution Note:

    This behaviour was recently changed; command line arguments containing double quotes and ending in backslash will preserve double quotes. For this reason, we recommend either not adding trailing backslash inside arguments used as directory paths or adding them as double backslash so escaping can be properly done.
    We are working on updating the Windows Editor command line options documentation to reflect these changes.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.