Search Issue Tracker
Fixed in 2018.2.X
Votes
6
Found in
2018.1.0b8
2018.1.0b13
Issue ID
1024461
Regression
Yes
When building the game for Windows, the .exe takes the file name of the folder you save in, instead of the given "Product Name"
To reproduce:
1. Build a new project
2. Observe that the .exe file's name is the same as the folder the .exe is in
Expected: Product Name, set in Player settings, should be used as the name of the executable. Alternatively, there should be a way to specify the name of the .exe file prior to building.
Reproduced in 2018.1.0b8, 2018.1.0b13, 2018.2.0a8
Did not reproduce in earlier versions, when building you were asked to specify the name of the .exe instead of the folder and thus there wasn't a problem with .exe taking the name of the folder
Comments (5)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector window flickers when a selector is created using a Style Class List Section
- [iOS] "UnityBatchPlayerLoop()" causes a freeze in the iOS application when it is put to the background and brought back to the foreground
- "Perform Selected" of Shortcut Manager window does not perform the shortcut in some cases
- Crash on mono_get_hazardous_pointer when running Play Mode tests in a specific project
- [iOS] ‘확인’(Done) and '취소'(Cancel) text is displayed as '...' in the on-screen keyboard when the System preferred language is set to Korean
APSchmidt
Oct 22, 2018 17:48
This issue is said to be fixed in 2018.2 but it's not.
The issue happens in 2018.2.13f1:
- building the project asks a destination where to save the built project,
- naming the executable is not possible,
- the executable takes the name of the project.
Baal_9
Jul 28, 2018 07:06
Currently not working for me, build is still being called folder name (ver 2018.1.5f1)
Naming errors occur in WebGL builds also.....
ybadragon
Jul 01, 2018 03:59
Reproduced in 2018.1.6f1. Didn't realize this was already reported when I made a duplicate bug....
Zarkow
Jun 05, 2018 12:09
Reproduced in 2018.1.2f1
Zarkow
Jun 05, 2018 12:08
This worked fine in 5.1.2, 5.2.3, 5.6.2, 5.6.3p1 and 5.6.3p1 (those are the projects I have on disk and can verify with).