Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1109539
Regression
No
Mismatch between assembly filename and metadata assembly name breaks ScriptableObject
How to reproduce:
1. Open the user's project
2. In the project window click Create -> What_The_Hack ModApi -> ScriptableObject dictionary
3. In the Inspector window change the Size to 1 and then set the Key to "asas" (Key name does not matter)
4. Save and Exit Unity
5. Open the project again
6. Select the SODictionary file that you've created
Expected result: You can modify the Scriptable Object
Actual result: The Inspector throws "The associated script can not be loaded." error
Reproducible with: 2017.4.22f1, 2018.3.7f1, 2019.1.0b5, 2019.2.0a7
Note: In 2017.4 versions, the Inspector does not show anything when selecting the Scriptable Object
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