Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.1.0a1
2018.1.5f1
Issue ID
1050962
Regression
Yes
UNITY_2017_4_OR_NEWER preprocessor is not recognised when using #if UNITY_2017_4_OR_NEWER in a script
To reproduce:
1. Open any script in any project
2. Add preprocessor #if UNITY_2017_4_OR_NEWER
Expected: UNITY_2017_4_OR_NEWER is recognized as preprocessor command
Actual: UNITY_2017_4_OR_NEWER is not recognized (code inside #if is not executed)
Reproduced in: 2018.1.0a1, 2018.1.7f1, 2018.2.0b11, 2018.3.0a3
Not reproduced in: 2017.4.6f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Tile Palette grid is moved after entering Play Mode
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Font Import Settings documentation page is missing when the documentation button is pressed in the Inspector window
Add comment