Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.6f1, 6000.2.0a11
Votes
0
Found in
6000.0.37f1
6000.1.0b5
6000.2.0a2
Issue ID
UUM-96819
Regression
No
User gets "EndLayoutGroup: BeginLayoutGroup must be called first." error during Xcode selection canceling
Steps to reproduce:
- Install 6000.1.0b5 build with "tvOS" module
- Create a new project
- If Xcode is installed please remove it (update 4/17/2025: I am able to repro this without uninstalling XCode, please view the bottom of this description + attached video)
- Go to File -> Build Profiles
- Select tvOS platform
- Find the "Browse" button next to the "Run in Xcode"
- Click it and click "Cancel"
- And again click it and again click "Cancel"
- Go to the Console window
Actual results: A screenshot is added below in the "Attachments" section. An error is displayed:
"EndLayoutGroup: BeginLayoutGroup must be called first.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:219)"
Expected results: No error.
Reproducible with versions: 2023.3.0b1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2
Not reproducible with versions: 2022.3.56f1, 2023.3.0a19
Can’t test with versions: -
Tested on (OS): Apple M1 Max - Sequoia 15.1.1, Windows
Different way to repro it:
- Install 6000.1.0b5 build with "tvOS" module
- Create a new project
- Go to File -> Build Profiles
- Select tvOS platform
- Find the dropdown menu next to "Run in Xcode"
- Click it, click on "Other" and click "Cancel"
- And again click "Other" and again click "Cancel"
- Go to the Console window
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
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Resolution Note (fix version 6000.2.0a11):
Verified fixed in