Search Issue Tracker
Won't Fix
Votes
3
Found in
5.3.1f1
Issue ID
771010
Regression
No
Creating asset through CreateAsset with HideFlags.HideAndDontSave throws error
Steps to reproduce:
1. Open attached project
2. In top menu, go to "Window -> ScripableObject Editor"
3. In input field enter some characters and press "Create"
4. Notice error in console:
!(o->TestHideFlag (Object::kDontSaveInEditor) && (options & kAllowDontSaveObjectsToBePersistent) == 0)
UnityEditor.AssetDatabase:CreateAsset(Object, String)
DataAssetCreator:CreateDataAsset(String, Object) (at Assets/Scripts/ScriptableObjects/Editor/DataAssetCreator.cs:9)
ScriptableObjectWindow:OnGUI() (at Assets/Scripts/ScriptableObjects/Editor/ScriptableObjectWindow.cs:41)
UnityEditor.DockArea:OnGUI()
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.2p4, 5.4.0b7
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team