Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2021.3.21f1
2022.2.10f1
2023.1.0b7
2023.2.0a6
2023.3.0a3
6000.0.0b11
Issue ID
UUM-29677
Regression
No
Elements are added incorrectly when in a nested list of SerializeReferences
Reproduction steps:
1. Open the “NestedListOfSerializeReferences“ project
2. Open the “SampleScene“ scene
3. Select the “Test” GameObject
4. In Inspector add an element to the list inside the “Script Compilation 1” foldout
5. Change any value of the added element
6. Add an element to the list inside the “Script Compilation 2” foldout
Expected result: the value changed only for the element in step 5, and the element added in step 6 is not empty
Actual result: all elements had their values changed in step 5, and the element added in step 6 is empty
Reproduced in: 2021.3.21f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a6
Could not test in: 2020.3.46f1 (compilation errors)
Reproduced using: macOS 13.2.1 (Intel), Windows 10 (by the reporter)
Reporter’s note: the desired behavior would be showing a “+” button with a small triangle. The said button would ask to select a fitting type. For example, [https://forum.unity.com/threads/serializereference-genericserializedreferenceinspectorui.813366/] or “ManagedReferenceField“ in [https://github.com/OscarAbraham/UITKEditorAid]
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.