Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a2
2020.1.0a9
Issue ID
1199278
Regression
Yes
Serializable generic class causes "You are trying to create a MonoBehaviour using the 'new' keyword." when class is declared
How to reproduce:
1. Open attached project "playground-2020.1a.zip" and scene "SampleScene"
2. Open "GenericBehaviour" script
3. Make any changes (make sure it compiles without errors)
4. Observe Console window
Expected result: no warnings are thrown
Actual result: "You are trying to create a MonoBehaviour using the 'new' keyword." warning is thrown
Reproducible with: 2020.1.0a2, 2020.1.0a15
Not reproducible with: 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2019.2.0a1
Could not test with: 2017.4 (due to MonoBehaviour class not detected, errors in Console window)
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):
Fixed in 2020.1.0a22