Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
1
Found in
6000.0.63f1
6000.2.15f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-130491
Regression
No
BuildOptions.Development is ignored when running a batch mode build for the win64 buildTarget
How to reproduce:
1. Unpack the "IN-122642_BatchBuild.zip" project to a convenient location
2. In project's Assets folder find the "batchbuild" file
3. Edit the “batchbuild” file, adding the path to the Unity.exe file of the needed Unity version on your computer into it
4. Run the modified "batchbuild" file
5. Locate the built application in "buildoutput" folder and run it
6. Observe the build window's bottom right corner
Actual result: The built application does not have "Development build" written in the bottom right corner of its window
Expected result: The built application has "Development build" written in the bottom right corner of its window
Reproducible with: 2023.1.0a26, 6000.0.63f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Could not test with: 2023.1.0a1 (Errors related to IL2CPP which couldn't be fixed)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- When building the application through the Editor as usual with "Development Build" checked, the issue does not occur
- As reported by user, this issue does not occur when running the same build for OSX target
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.'
The issue in this reproduction project is caused by the batch file generating two separate builds.
The first is a non‑development build created by the command -buildWindows64Player buildoutput/build.exe.
The second is produced by the custom build method com.magicfuelgames.unitybatchmodeexecute.BatchModeExecute.UnityBatchModeExecuteMethodWindows.
If the intention is to build only through the custom method, the line that invokes -buildWindows64Player buildoutput/build.exe must be removed from Assets/batchbuild.bat.
In addition, the output path defined in BuildConfigurator.cs (located under Packages/com.magicfuelgames.unitybatchmodeexecute/Editor, around line 356) should be updated so that the custom build method writes to buildoutput/build.exe.
After applying these changes, Unity will correctly generate a single development build in the %ProjectPath%/buildOutput directory.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.'
The issue in this reproduction project is caused by the batch file generating two separate builds.
The first is a non‑development build created by the command -buildWindows64Player buildoutput/build.exe.
The second is produced by the custom build method com.magicfuelgames.unitybatchmodeexecute.BatchModeExecute.UnityBatchModeExecuteMethodWindows.
If the intention is to build only through the custom method, the line that invokes -buildWindows64Player buildoutput/build.exe must be removed from Assets/batchbuild.bat.
In addition, the output path defined in BuildConfigurator.cs (located under Packages/com.magicfuelgames.unitybatchmodeexecute/Editor, around line 356) should be updated so that the custom build method writes to buildoutput/build.exe.
After applying these changes, Unity will correctly generate a single development build in the %ProjectPath%/buildOutput directory.