Search Issue Tracker
Fixed in 2020.1.0b2
Fixed in 2021.1.X
Votes
2
Found in
2021.1.0a7
2021.1.0b1
Issue ID
1302915
Regression
Yes
"Month must be in range [1-12]!" errors are thrown in the Console when opening a project
How to reproduce:
1. Create a new project or open an existing one
2. Observe the Console
Expected result: No visible errors present
Actual result: Multiple "Month must be in range [1-12]!" errors appear in the Console
Reproducible with: 2021.1.0a7, 2021.1.0b1
Not reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0a6
Comments (1)
-
Peter77
Jan 04, 2021 10:54
Related forum thread:
https://forum.unity.com/threads/month-must-be-in-range-1-12.1031107/
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
- 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
Resolution Note (fix version 2020.1.0b2):
Fixed in 2021.2.0a1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b2