Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4.6f1
2020.2
Issue ID
1273706
Regression
No
[ScriptableObject] Script loses reference to ScriptableObject after compilation error is encountered and then fixed
Reproduction steps:
1. Open attached project "Scriptable.zip" and scene "ScriptableObjectIssue"
2. In Project window, open "MyBuggyScript.cs"
3. In "MyBuggyScript.cs", uncomment line 7
4. Restart Unity Editor
5. In "MyBuggyScript.cs", comment out line 7
6. In Hierarchy window, select "My SO Container" GameObject
7. Observe "My Scriptable Object" field
Expected result: There is a reference to the scriptable object
Actual result: There is no reference to a scriptable object
Reproducible with: 2018.4.27f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Comments (1)
-
ChrisIceBox
Sep 01, 2020 08:01
The object is not unsaved - the data is lost. Please re-open this issue. Data that was part of the scene file being is lost.
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
The behavior for unsaved assets is undeterministic in this scenario, in order to address this you should save the asset in the asset database at creation time: AssetDatabase.CreateAsset(myScriptableObject, "Assets/MyScriptableObject");