Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a10
2019.2.0a1
2019.3.0a1
2019.3.0a7
Issue ID
1167102
Regression
No
ExpressionNotValidException errors appear when adding invalid versions to Version Defines list
How to reproduce:
1. Create new project
2. Create Assembly Definition
3. Add to Version Defines list
4. Select any package
5. Write any information to Define and Expression fields and apply.
Reproducible with: 2019.1.0a10, 2019.1.9f1, 2019.2.0b8, 2019.3.0a8
Not reproducible with: 2017.4.29f1, 2018.4.3f1, 2019.1.0a9 (Version Defines weren't available)
Actual results: ExpressionNotValidException spams the console
Expected results: only one error explaining the issue should appear
Error: ExpressionNotValidException: Invalid character a : a
UnityEditor.Scripting.ScriptCompilation.SemVersionRanges.ParseExpression (System.String expression) (at C:/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/SemVersionRanges.cs:95)
Fixed in: 2020.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment