Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0b6
Issue ID
879044
Regression
No
Re-importing a script makes created ScriptableObject's data null when using AssetDatabase.LoadAssetAtPath<T>
To reproduce:
1.Download and open attached project.
2.Go to Editor folder and remove "AndroidKeystoreData" ScriptableObject.
3.Re-import "AndroidKeystoreData.cs" script.
4.Notice the values that are outputted in the console.
5.Re-import "AndroidKeystoreData.cs" script again.
6.Notice that values taken from that same ScriptableObject are null.
Expected result: Scriptable object's values are shown in the console.
Actual result: Shown values are null.
Reproduced with: 5.6.0b7, 5.5.1p3, 5.4.4p2.
Notes: If You select "AndroidKeystoreData" ScriptableObject ,saved data is shown in the inspector, but it shown as null in the console when accessed trough script.
Verified with 2017.2.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Add comment