Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2022.1.0a12
2022.1.0f1
2022.2
Issue ID
1428325
Regression
Yes
Console error when Serialized property in the nested array is removed
Reproduction steps:
1. Open the user's attached project
2. Select the "Example Hierarchy" (Assets > Example Hierarchy)
3. Navigate to the Example Hierarchy window (Window > Nexerate Nodes > Node Hierarchy)
4. Right click "Root" node, then (Example > Node) to create a new "Example Node"
5. Select the created "Example Node" and add a component to it (Example node > Add Component > Example)
6. Right-click the "Example Node" and delete it (Example Node > Delete)
7. Select the "Root" node, and the error should appear in the Console
Expected result: No error is shown in the Console
Actual result: Error is shown "SerializedProperty nodes.Array.data[7] has disappeared!
UnityEditor.RetainedMode:UpdateSchedulers ()"
Reproducible with: 2022.1.0a12, 2022.2.0a12
Not reproducible with: 2021.3.6f1, 2022.1.0a11, 2022.2.0a13, 2023.1.0a4
Couldn't test with: 2019.4.40f1, 2020.3.26f1 (Is not compatible with Nexerate Nodes framework)
Reproducible on: Windows 10 Pro (20H2)
Notes:
- Project uses the Nexerate Nodes framework: https://github.com/Nexerate/nodes.git
- 2019.4 and 2020.3 does not support the Nexerate Nodes framework
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a13