Search Issue Tracker
Fixed
Fixed in 6000.0.37f1, 6000.1.0b5, 6000.2.0a1, 7000.0.0a17
Votes
0
Found in
6000.0.35f1
6000.1.0b3
6000.2.0a1
7000.0.0a1
Issue ID
UUM-93248
Regression
Yes
"AssertionException: Assertion failure. Value was False" error is thrown when unmaximizing a docked UI Builder Window
Steps to reproduce:
1. Create a new project
2. Create a new UI Document (Assets > Create > UI Toolkit > UI Document)
3. Open the created UI Document
4. Dock the UI Builder Window anywhere
5. Double click on it to maximize it
6. Double click on it to unmaximize it
7. Observe the Console
Expected result: No errors are thrown
Actual result: "AssertionException: Assertion failure. Value was False" error is thrown constantly
Reproducible in: 6000.0.34f1, 6000.0.35f1, 6000.1.0b3
Not reproducible in: 2021.3.47f1, 2022.3.56f1, 6000.0.33f1
Reproducible with: Windows 11
Not reproducible with: No other environment tested
Note: The error throwing is stopped once the Tab is closed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment