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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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");