Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
1
Found in
2020.1.0a7
2020.1.0b8
2020.2
Issue ID
1247409
Regression
Yes
[Scripting] NamespaceParser fails when ScriptableObject class is inside a custom namespace
How to reproduce:
1. Open user's attached project
2. Select the "Test" ScriptableObject in the Project window (Assets folder)
3. Observe the Inspector
4. Create a new ScriptableObject (Create -> Baz)
5. Select the new ScriptableObject and observe the Inspector
Expected result: Test.cs script is assigned in the Script property
Actual result: Test.cs script is not assigned in the Script property
Reproducible with: 2020.1.0a7 2020.1.0b9, 2020.2.0a11
Not reproducible with: 2017.4.40f1, 2018.4.23f1, 2019.3.14f1, 2020.1.0a6
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.2):
Fixed in: 2020.2.0a13
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b11