Search Issue Tracker
Fixed
Fixed in 2023.1.0a9
Votes
2
Found in
2021.2.19f1
2021.3.0f1
2022.1.0b16
2022.2.0a10
2023.2.0a1
Issue ID
UUM-712
Regression
No
PlayerSettings.SetScriptingDefineSymbols doesn't set symbols when buildTarget parameter doesn't match current Build Target
How to reproduce:
1. Open the user-submitted project
2. Open the Build Settings window and change the Platform to 'Windows, Mac, Linux' (File > Build Settings... > Switch Platform)
3. In the top menu bar, select 'Test > Run'
4. In the File Explorer, open the project folder and run test.exe inside the _Output folder
5. Observe the last 3 lines of the Console output
Expected result: The message 'MY_SYMBOL is defined.' is seen
Actual result: The message 'MY_SYMBOL is not defined. (AAAAAAAAAAAAAAAAA)' is seen
Reproducible with: 2021.2.19f1, 2021.3.0f1, 2022.1.0b16, 2022.2.0a10
Could not test with: 2019.4.37f1, 2020.3.33f1 (Dedicated Server Build Target is unavailable)
Comments (1)
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
- Shader Graph Material is left in broken state when switching from a .git branch with no HDRP to a branch that contains HDRP
- Crash on buffer_add_value_full when hovering over SerializedProperty.boxedValue in Debug Mode after ISerializationCallbackReceiver.OnAfterDeserialize modifies value
- Editor is not capitalised consistently in Preferences window
- [Linux] “Restore Defaults” warning window appears behind Profiler Modules dropdown
- [iOS] Time.deltaTime is switching between 9.998583E-06 and approximately 0.01 seconds
Peter77
Apr 11, 2022 14:32
Related forum thread:
https://forum.unity.com/threads/case-1413904-playersettings-setscriptingdefinesymbols-does-not-work-correctly.1257972