Search Issue Tracker
By Design
Votes
0
Found in
2018.2.16f1
2019.4
2020.3
2021.2
2022.1
Issue ID
1103080
Regression
No
PlayerSettings.SetScriptingDefineSymbolsForGroup has inconsistent behaviour in batch mode
How to reproduce:
1. Download the attached file “1103080.zip” and unzip it
2. Run “<path to Unity.exe> -batchMode -buildTarget Android -projectPath <path_to_project> -executeMethod MyBuild.DoBuild -logFile android.txt -quit” in the command line
3. Download the attached file “1103080.zip” and unzip it again
4. Run “<path to Unity.exe> -batchMode -buildTarget iOS -projectPath <path_to_new_project> -executeMethod MyBuild.DoBuild -logFile ios.txt -quit” in the command line
5. Open the generated logs
Expected result: both platforms have the same amount of recompilations
Actual result: the amount of script recompilations is different depending on the platform set in the script
Reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
Notes:
- Change “<path to Unity.exe>” and “<path_to_project> / <path_to_new_project>” to paths where the Editor and the project is located
- Step 3 can be replaced by reverting changes using version control tools
- It’s not an iOS specific issue, the platform in MyBuild.cs can be changed to any platform
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
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Resolution Note:
This is expected, as some player settings require a script reload for the settings to be applied. So we will close this by design. We created documentation tickets to mention this behavior.