Search Issue Tracker
Fixed
Fixed in 2022.2.21f1, 2023.1.0b18, 2023.2.0a15
Votes
7
Found in
2021.2.0a4
2021.2.7f1
2022.1.0b2
2022.2.17f1
2023.1.0a1
2023.2.0a1
Issue ID
UUM-3432
Regression
Yes
Error "GUI Error: Invalid GUILayout state" when using BeginVertical
Reproduction steps:
1. Open user's attached project
2. Select GameObject in the Hierarchy
3. In the Inspector find Script Component and press "Open Window"
4. At the popped up window press the Material selector
5. Observe Console error
Expected result: No errors are thrown when using custom GUILayout
Actual result: "GUI Error: Invalid GUILayout state" error is thrown
Reproducible with: 2021.2.0a4, 2021.2.7f1, 2022.1.0b2
Not reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.1.28f1, 2021.2.0a3
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
ghosthjt
Aug 12, 2023 05:27
GUI Error: Invalid GUILayout state in AddressableAssetsWindow view. Verify that all layout Begin/End calls match
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
unity 2022.3. still have this issue.
Aka_ToolBuddy
Apr 26, 2023 12:17
For more information, head to the forum thread I posted about this issue:
https://forum.unity.com/threads/avoiding-you-getting-insane-because-of-invalid-guilayout-state-errors.1429669/
Aka_ToolBuddy
Apr 26, 2023 11:43
Found the reason: Some Unity UI components (such as a material selector) throw ExitGUIException exceptions as part of their regular, non exceptional, code flow. This exception when thrown inside a GUILayout.BeginX/EndX block, stops the EndX method from being called, leading to the error described above