Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.4f1
2019.1.0a1
2019.2.0a1
Issue ID
1123657
Regression
No
[Windows] Calling Undo after DeleteArrayElementAtIndex sets the values to 0
How to reproduce:
1. Download and open my attached empty project "UndoTestProject.zip"
2. Right click on "Assets" folder, select "Create" and then "Undo Test" to create a scriptable object
3. In the Inspector, I have pressed on a spinning wheel(Context menu) and pressed on "Fill Data"
4. Press Ctrl+Z to undo changes and notice that some values of Element 3 are "0"
Expected result: Calling Undo(CTRL+Z) after DeleteArrayElementAtIndex sets the values to 0
Actual result: Calling Undo(CTRL+Z) after DeleteArrayElementAtIndex sets the values to 0
Reproducible with: 2018.3.7f1, 2019.1.0b5, 2019.2.0a7
Note: Marked this issue with a "Windows" tag since it is not reproducible on iOS.
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
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 issue.