Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2018.4.35f1
2019.4
2020.3
2021.1
2021.2
Issue ID
1338709
Regression
No
|| operator is not supported for define constraints in 2018.4 LTS
Reproduction steps:
1. Open the project in "PluginTesterProject2018.zip"
2. In the Project window select Assets/Plugins/Plugin Test
3. In Inspector delete all define constraints
4. Add define constraint named "DEVELOPMENT_BUILD || UNITY_EDITOR"
Expected result: there are no errors, the constrain is successfully added
Actual result: PrecompiledAssemblyException: Invalid define constraint DEVELOPMENT_BUILD || UNITY_EDITOR is thrown and the define constraint gets removed
Reproducible with: 2018.4.35f1
Not reproducible with: 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a18
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note:
As the issue is only reproducible in 2018.4 we will not be doing anything further, as 2018.4 is out of support and will not receive anymore updates.
The issue is fixed in 2019.4, so upgrading to a newer Unity LTS will fix the issue. As a work around it would require having two assemblies with their individual target. One editor and one standalone. Then you would be able to put define constraints on them respectively.