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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a13
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b11