Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.41f1
Issue ID
UUM-18615
Regression
No
EndLayoutGroup BeginLayoutGroup must be called first error appears when "Undo" shortcut is pressed
Steps to reproduce:
1. Download and open the attached project
2. Select the "LayeredLit" material in the Project window
3. In the Inspector window, open the color picker
4. Change the material's color
5. Press the "Control" + "z" buttons
Expected outcome: No errors appear in the console window
Actual outcome: "EndLayoutGroup: BeginLayoutGroup must be called first.
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()" error appears in the console window
Reproduced with: 2020.3.41f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a18
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
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue, the number of users affected by it and it’s current experimental state. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2020.3.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue, the number of users affected by it and it’s current experimental state. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.