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
- Joint Physics result in unexpected behaviors when used for articulated vehicles like buses or trucks
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts which worked with TMP Font Asset Creator
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.