Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.10f1
Issue ID
1085225
Regression
No
PlayerSettings.SetScriptingDefineSymbolsForGroup behaves differently when running in batchmode
How to reproduce:
Editor:
1. Open the user's attached project
2. In the menu bar go to Build and select Build Player
Batch Mode:
1. Launch Unity with these arguments:
-batchmode -executeMethod "BuildScript.Build" -projectPath "<Project Path>" -quit
(Replace <Project Path> with the project path)
Expected result: Unity behaves the same way in both Editor and -batchmode, which means that either both complete the build or both fail
Actual result: Unity behaves differently in Editor and -batchmode, which results in Editor completing the build and -batchmode failing
Reproducible with 2017.4.13f1, 2018.1.9f2, 2018.2.12f1
Not reproducible with 2018.3.0b6, 2019.1.0a4
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
- Game View Tab Scale changes erratically when a Unity Tab is on a different screen with a differing Display Scale
- Six way lighting receiving wrong lighting from APV when set to World Space
- Crash on SortByExecutionOrder when interrupting the .androidpack import process
- ShaderGraph tab header changes the icon to the VFX Graph icon when ShaderGraph and VFX Graph with the same name are both opened
- The Build Profiles window has usability issues when the panel takes up less than 30% of the screen width
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.